It's related to my post "How Does SQL Reuse Data Pages?", which you replied to as well. When a new row is inserted, SQL uses the IAM page to find an extent with free space. So, in trying to figure out how SQL determines where a new row will get inserted, I believe I'd need to know extent information along with the page information returned by sys.fn_PhysLocFormatter. In my testing, it seemed odd the way SQL would go back and reuse an "old" page. My accurately, it seemed odd "when" SQL would decide to go back and reuse an "old" page. I think I need to take into account extents to make some sense of it all, and not simply look at the pages.

From "Managing Space Used by Objects" in Books Online;

When the Database Engine has to insert a new row and no space is available in the current page, it uses the IAM and PFS pages to find a page to allocate, or, for a heap or a Text/Image page, a page with sufficient space to hold the row. The Database Engine uses the IAM pages to find the extents allocated to the allocation unit. For each extent, the Database Engine searches the PFS pages to see if there is a page that can be used. Each IAM and PFS page covers lots of data pages, so there are few IAM and PFS pages in a database.

I think I need to look at when an entire extent has become full, and then see where SQL starts inserting the new rows, keeping in mind that SQL looks for free space by searching extents, not simply by searching pages.

Thanks again for your input. I think I can modify my SELECT statement to return an integer representing the extent each page belongs to (simply meant to help me "group" pages together).