Page Number in SQL Server database is not starting from zero
Let me preface this answer with the statement that there could be entire books written on this subject and this is without a doubt some of the most interesting and complicated parts of SQL Server.

This answer will not attempt to go into great lengths of detail, but a simplified overview of certain items.


  Q 1). Why my page not starting from 1:0 or 1:001?


In SQL Server there is the logical structure of your database and the physical. Since you're asking about the physical structure, there are two things at play here:


Internal data structures and tracking
Internal metadata storage


Your table doesn't start at page 0 of file 1, however that space in indeed occupied and used. This page is reserved and called the file header page, each file will have one of these.

Additionally there are GAM intervals which happen roughly every 4 GB, PFS that happen every roughly 64 MB, etc.

Finally there are the metadata tracking tables, such as sys.sysschobjs, which aren't readily available for consumption yet do need space in the database.


  Q 2).Will this page number have dependency from model database?


Simplistically speaking, yes. The more objects created and inherited from model, the more internal tracking and space that will be needed. This is grossly over simplified but should do, given the previous explanation as data can be extrapolated from it.

That's just the beginning ...

Allocation algorithms in SQL Server may be different between base objects. For example, when to allocate a new page may differ between heaps and clustered indexes. Where the data is allocated depends on how long the database has been in use, where it has been internally last filled to, and a host of many other different variables.

It truly is very interesting stuff and it's great to have fun with.