Where this site's data comes from
Every dataset behind Jersey Properties, where it originates, how often it's meant to refresh, and — unlike a static methodology page — a real timestamp read directly from this site's own storage for when it was last actually written, plus the newest date embedded in the data itself where one exists. Nothing on this page is a hardcoded guess: the "Last written" column comes from R2 object metadata at request time, and every "on file" figure is a live count over the real data.
| Dataset | Source | Refresh cadence | Last written to storage | Freshest date in the data | On file |
|---|---|---|---|---|---|
| Listings, prices & photos Every current for-sale and to-rent listing shown on this site | Each agent's own public website (49 agents with live stock) | Nightly, 04:10 UTC | 22 Aug 2026, 13:01 UTC | Build dated 2026-08-19 | 1,953 listings |
| Estate agents directory Which agents this site tracks and how many live listings each has | Each agent's own public website | Refreshed alongside the listings snapshot above | 22 Aug 2026, 13:01 UTC | — | 69 agents |
| Sold prices since 2001 Every recorded property sale, address, date and price | Places.je property transaction register (Government of Jersey) | Weekly, Monday 03:15 UTC | 22 Aug 2026, 13:01 UTC | Newest sale on file: 31 Jul 2026 | 33,545 sales |
| Planning applications Every planning application on the public register, with description, decision and dates | Government of Jersey Planning Register | Nightly, 02:15 UTC | 22 Aug 2026, 13:01 UTC | Newest decision on file: 18 Aug 2026 · newest received date: 24 Jul 2026 | 3,402 applications |
| Daily stock snapshots This site's own count of live listings, by market and agent, taken once a day | Computed from the listings snapshot above, not a separate external source | Nightly, cron started 21-Aug-2026 | 22 Aug 2026, 05:00 UTC | Newest snapshot: 22 Aug 2026 | 1 day on file |
| What left the market Listings present yesterday and gone today, with the reason the agent gave (sold/let/withdrawn) | Derived from consecutive daily stock snapshots, same cron as above | Nightly, cron started 21-Aug-2026 | Not written yet | No departures recorded yet | 0 days with departures on file |
| Listing first-seen dates How long each live listing has been tracked by this site | Derived from the daily stock snapshot, forward-only from 21-Aug-2026 (see /stock-history) | Nightly, cron started 21-Aug-2026 | 22 Aug 2026, 05:00 UTC | — | 1,871 listings tracked |
| Listing price history Observed asking-price changes per listing (not the agent's own "Reduced" badge) | Derived from the daily stock snapshot, same cron | Nightly, cron started 21-Aug-2026 | 22 Aug 2026, 05:00 UTC | — | 0 listings with an observed change |
| Monthly market report Sold prices, planning decisions and stock levels, summarised once a month | This site's own sold-register/planning/listings data, aggregated | Monthly, 1st of the month | Not written yet | No report generated yet | 0 months on file |
| Site health checks Automated sweep confirming key pages still return real content | This site's own nightly self-check | Nightly | 22 Aug 2026, 15:25 UTC | Latest run: 2026-08-22 — 35 passed, 0 failed | 1 run on file |
| Listed buildings & places Every entry on Jersey's Historic Environment Record — reference, property, road, parish, grade and description | Government of Jersey Historic Environment Record | Weekly, Monday 03:45 UTC | 22 Aug 2026, 15:06 UTC | — | 4,265 entries |
What "Last written" means
This is when the underlying file in this site's storage was last overwritten — read live via a HEAD request against the object, not a cached or remembered value. It moves only when the relevant cron actually runs and produces new data, so two datasets refreshed on very different schedules (nightly planning vs a one-off listings snapshot) will show very different ages here, honestly.
What this page deliberately doesn't do
It doesn't smooth over the gap between "refresh cadence" (what's supposed to happen) and "last written" (what actually has) — the first few days after a new cron ships, expect to see "No … written yet" here, and that's the honest state, not a bug. See what's changed for the same underlying data read as a change digest, and about & methodology for how each dataset is actually used and what this site infers from it.