All insights

Investing framework · 2026

Understanding rental transaction data: what it does and doesn't tell you

By Winfred Quek · 8 minute read · Published 13 July 2026

Investing framework · Data literacy

Understanding rental transaction data: what it does and doesn't tell you

By Winfred Quek, Associate Marketing Consultant · CEA R073319H · Crestbrick Pte Ltd (L31010886H) · Published 13 July 2026

Quick answer: Singapore's published rental transaction data, whether from URA for private property or HDB for public flats, is genuinely useful but narrower than it looks. It reports contract rent, the base monthly figure in the tenancy agreement, excluding utilities, agent fees and any other costs bundled into the arrangement between landlord and tenant. There is a reporting lag between when a lease is signed and when it appears in the data, so the most recent period is typically incomplete and understates real activity. And median or average figures calculated from a small number of transactions in a given period can be swung significantly by one or two atypical leases. None of this makes the data unreliable, it makes it a tool that needs to be read with its limitations in mind, not taken at face value as the full picture of achievable rent.

Facts verified: 13 July 2026 · No specific rental figures cited · Sources attributed below

Rental data is the number landlords and tenants both reach for first, because it looks precise, official and reassuringly objective compared to an agent's verbal comparable or a portal listing's asking price. That precision is partly an illusion. The data is real and the source is authoritative, but what it actually captures, and what it leaves out, matters enormously for anyone using it to price a lease or evaluate a rental yield. I want to walk through exactly what is in the number, what is not, and how to read it without being misled by its apparent exactness.

What "contract rent" actually captures

Published rental transaction data reflects contract rent, the base monthly figure agreed and stated in the tenancy agreement between landlord and tenant. It does not, as a rule, capture what else might be bundled into that arrangement: utilities, internet, cleaning services, furniture packages, or agent commission arrangements that vary by deal. Two leases showing an identical contract rent in the published data can represent quite different total costs for the tenant and different net proceeds for the landlord, depending on what else is included.

This matters most when you are comparing your own unit's rental readiness against published comparables. If nearby transactions show a certain contract rent but you know from experience that fully furnished units in that development typically carry a premium, or that landlords there commonly absorb utilities as part of the deal, the raw contract rent figure alone will understate or overstate what you should actually expect. For the full mechanics of computing what a unit really nets you after these costs, see my rental yield versus appreciation guide.

The reporting lag: why the latest period looks softer than it is

There is an inherent lag between when a tenancy agreement is actually signed and when the transaction appears in published data, because the lease has to be reported and processed before it shows up in the dataset. The practical effect is that the most recent period shown, whether that is the latest month or quarter, is almost always incomplete at the point you are viewing it, with more transactions still to be added as processing catches up. Reading a dip in the newest period as a genuine cooling in the rental market is a common and avoidable mistake, when it may simply be a data completeness issue that resolves itself over the following weeks as more contracts are recorded.

Always check the as of date. Treat the most recent one or two periods shown in any rental dataset with more caution than the established trend before them, and never draw a strong conclusion, especially a pricing decision, from the newest data point in isolation.

Why a small sample can mislead you badly

A median or average rent figure is only as reliable as the number of transactions behind it. For a development or unit type with high rental turnover, dozens of transactions in a given period, the median is a genuinely informative number, smoothing out individual outliers. For a smaller or less liquid segment, a boutique development, an unusual unit type, or simply a quiet month, the same calculation might be based on a handful of transactions, and a single atypical lease, a large penthouse, a short diplomatic posting lease with unusual terms, or a related party transaction, can swing the reported median substantially.

The practical habit worth building is to always check the transaction count behind any median or average you are relying on, not just the headline figure. A median built from three transactions deserves far less confidence than one built from thirty, even though both are presented with the same apparent precision on a chart or table. This same discipline applies when reading sale transaction data, and my guide to checking property transaction history covers the sale side of the same underlying issue.

What the data does not tell you about unit condition or terms

Contract rent is a single number that compresses a lot of unstated context: the unit's renovation state, whether it came furnished or unfurnished, the lease length and any rent free fitting out period, whether a diplomatic clause was included, and the specific negotiating dynamics between that particular landlord and tenant. A transaction at a below average rent might reflect a landlord eager for a quick let, a unit in original, dated condition, or simply a longer lease term traded for a lower monthly figure. None of that context survives into the published number.

This is the same reason two seemingly identical units in the same stack can command genuinely different achievable rents in practice, something I cover in more depth in my rental yield by property type guide. Published data gives you a starting range, not a guaranteed number, and the gap between the two is exactly the value an experienced eye on the ground adds when pricing a specific unit.

How to actually use the data well

  1. Pull the underlying transaction count, not just the summary median, before trusting any rental benchmark for a specific development or unit type.
  2. Discount the most recent one to two periods for reporting lag, and look at the established trend rather than the freshest single data point.
  3. Treat contract rent as a base, not a full cost comparison, and ask what else, utilities, furniture, agent fees, is typically bundled in your specific market segment.
  4. Widen your comparable set across a few similar developments and adjacent periods when a single development's own data is thin, rather than anchoring to one small sample.
  5. Cross check against what agents and landlords on the ground are actually seeing, since real time market feedback often reflects conditions faster than published data can catch up to.

Frequently asked questions

Does published rental data include utilities and agent fees?

No. Published rental transaction figures reflect contract rent, the base monthly rent in the tenancy agreement, and generally exclude utilities, agent commission and other bundled costs. Two units with the same published rent can have different all in costs depending on what else is included in the lease.

How current is the rental data I see on property portals or URA?

There is a reporting lag between a tenancy agreement being signed and appearing in official data, so the most recent period shown is typically incomplete and can understate actual leasing activity. Always check the data's as of date and treat the very latest period with more caution.

Why can median rent for a project be misleading?

A median calculated from a small number of transactions can swing significantly based on one or two atypical leases. Developments with low rental transaction volume in a given period are especially prone to this. Check how many transactions a median is based on before trusting it.

Where can I check actual rental transactions for a specific project in Singapore?

URA publishes private residential rental contract data, searchable by project, through its REALIS platform, showing individual contracts including unit size band, floor level range and rent. HDB publishes separate statistics for public housing flats. Check both against portal estimates or agent quoted comparables rather than relying on either alone.

Pricing a lease or checking a rental yield?

Reading published rental data properly, adjusted for sample size, lag and what is actually included, is the difference between an accurate yield model and a misleading one. A Property Portfolio Analysis grounds your numbers in a properly read comparable set.

Book a free analysis call

Sources & references

Winfred Quek is Associate Marketing Consultant at Crestbrick Pte Ltd, advising Singapore upgraders, investors and families. CEA R073319H. The information on this page is general and does not constitute investment or financial advice. No specific rental figures are cited or implied. Verify current data via official sources before pricing any lease or making any investment decision.

Related guides