Methodology

How we calculate our market data

Every number on imotesa.bg comes from public listings put through the same process. This page describes that process — including what the data cannot show.

Data sources

The data comes from publicly available Bulgarian property listings published on the major property portals. We do not use Registry Agency records, notarial deeds or any other register of completed transactions — see “Limitations”.

Listings are crawled every hour; statistics are recalculated every four hours. Crawling is automated and runs every hour. A listing not found during crawling for 24 hours is marked inactive and excluded from all statistics. A listing removed from its source a few hours ago may therefore remain active on our site for a while.

Market figures are calculated using active listings only. Inactive listings are kept for price history but excluded from the median calculations.

imotesa.bg statistics (typical prices, percentiles, indices and scores) are published under CC BY 4.0 — free to reuse with attribution. The licence does not cover source listings, photos or descriptions.

Current coverage

  • 210,000+Active Listings
  • 20,000+Merged Listings
  • 480+Neighbourhoods with Score
  • 250+Cities & Regions

Duplicate detection

The same apartment is often listed by several agencies across several portals at once. If these listings are counted as separate properties, they skew every statistic towards the properties advertised most aggressively.

Listings are therefore grouped into a single property record based on two independent signals:

  • Photo similarity — the system compares images by visual similarity, so the same photo can be recognised even when it is published in a different file format or has been edited. This allows listings for the same property to be linked without relying solely on identical image files.
  • Attribute matching — location, floor area, storey, year built and price. An image match without an attribute match is not enough — this prevents listings for different apartments in the same building from being merged just because they use the developer's stock photos.

The merged record keeps all listings for the property, so its page shows which agency offers it at which price. Where prices differ, one listing per property is used in the market calculations, rather than the average price of the duplicate listings.

Detection is not infallible. A listing with no photos and sparse attributes may survive as a separate property; the opposite error — merging two near-identical neighbouring apartments — is rarer but possible.

Median, not mean

The published prices are medians: values with an equal number of listings above and below them. A mean is heavily influenced by a small number of very expensive properties and would describe a market most buyers would not recognise. The median describes the typical listing.

We use “average prices” in page headings because that is what users search for. Wherever we show a specific value, it is labelled as a median or typical price.

A segment is published only when it contains enough listings for the median to be stable. The thresholds differ by property type:

Minimum active listings per segment
Property typeMinimum listings
Apartments, studios, single-room units15
Houses and floors of houses8
Parking spaces and garages5

Segments with fewer listings than the minimum threshold have no page or headline price. They appear only as rows marked “limited data” in neighbourhood tables.

Segments are calculated at four levels: neighbourhood and room count, neighbourhood overall, city and room count, city overall. Each level must clear the threshold on its own.

The “% below market” signal

The badge on a listing compares its price per square metre against the median price per square metre for the segment the property falls into:

deviation = (segment median €/m² − listing €/m²) ÷ segment median €/m²

The most specific segment with sufficient data is used, in this order: neighbourhood and room count → neighbourhood (regardless of room count) → the city as a whole. That last step allows properties in towns with no named neighbourhoods, and property types where room count is not used for comparison (houses, parking spaces), to receive a signal too.

The badge’s colour depends on where the price falls among similar properties, rather than just its percentage deviation. Below the 25th percentile, the property is cheaper than three quarters of properties in the segment and is labelled as cheaper than the market. Above the 75th percentile, it is labelled as more expensive. Between these boundaries, it is within the typical range, even if it is 20% away from the median. A warning appears only when the price is among the lowest or highest 10% in the segment and at least 40% below or 67% above the median, in a segment of at least 20 properties with a plausible floor area. A gap like that usually means a data error or something the listing does not mention.

This is not a valuation. The signal does not account for condition, aspect, floor, noise, view, build quality or legal status — the things that explain much of the price difference. It shows where the asking price sits relative to neighbouring listings, and nothing more.

How we measure price reductions

The “Price cuts” series reports one thing only: how many sellers reduced the ADVERTISED price of a live listing during the month. These are the exact rules.

  • Asking prices, not transaction prices — we measure changes to published prices on live listings. These are not discounts negotiated during a sale, so our figure is not comparable with the percentages from broker surveys — the two describe different quantities.
  • What counts as a reduction — any recorded price lower than the one before it. A listing's first recorded price is its initial asking price and is never counted as a reduction. Changes under 1% are treated as rounding and ignored — in practice they are about 14% of all reductions and would distort every figure.
  • Which measure can be compared across months — the share of reductions among ALL price changes. Reductions and increases are both detected the same way — when we crawl a known listing again — so their ratio does not depend on how many listings we checked during the month. The number of sellers who reduced their prices, and their share of active listings, depend on our coverage. They are therefore published only for the current month and are not used to track trends.
  • The denominator — the share of active listings is measured against the count of active apartment sale listings for the same city and month in our monthly statistics — the same series the imotesa index is built on, so the two measures remain consistent. When that count is missing for a month, the share is simply not published.
  • Neighbourhood data covers three months — the neighbourhood table covers the last three months, while all headline figures in the article are monthly. For individual months, the samples are too small for reliable comparisons between specific neighbourhoods. Each neighbourhood’s share is calculated against the AVERAGE number of active listings across the three months — a property active in all three counts once. If data is missing for any of the three months, only the count is shown, without a share.
  • Publication thresholds — an analysis for a city is published only if at least 50 sellers reduced their prices during the month; a typical reduction requires at least 20 reductions, and a distribution of reduction sizes requires at least 50. A neighbourhood is included only if at least 10 sellers reduced their prices and there were at least 30 active listings over the period. Sometimes there is no monthly analysis for one of the four cities because its sample is below the publication threshold.
  • From which month onward — our crawl coverage grew substantially during the first half of 2026. Counts of price reductions before March 2026 reflect our limited coverage at the time rather than the whole market, so they are not published. For the same reason, the number of sellers who reduced their prices and their share of active listings at the start of the series should not be used for comparisons between months. The share of reductions among all price changes is used for that purpose.
  • Methodology version — every record includes the version number of the methodology used to calculate it. If we change the methodology, existing records keep their version and the change is announced here. This allows every published value to be checked against the method used to calculate it.

imotesa index — how it is computed

“imotesa index” is a monthly measure of typical apartment prices in Bulgaria. It tracks two separate groups of locations — cities and resorts. These are the rules used to calculate it.

  • The composition is fixed and does not change every month — the national index covers 16 pre-selected regional capitals. The composition is fixed: if a city’s listing count later falls below the minimum threshold, the city stays in the index. A new city is added only when a change in composition is announced — see “Rules for changes to the index” below. We do not describe the index as covering “the biggest cities” in the country, since selection is based on available listing data rather than population.
  • The resort sub-index is separate — 9 coastal and mountain resort locations are reported separately from the city index. Resort markets have different, strongly seasonal supply patterns, and including them would distort the national figure. Separate typical prices and active-property counts are published for the resort sub-index. It has no index value of its own (base = 100), since the index has a single base month that cannot meaningfully apply to two different groups of locations.
  • Base month: June 2026 = 100 — data for earlier months in our database (January–May 2026) was calculated using a different method, based on listing activity throughout the month rather than on a specific date. The figures are therefore not directly comparable with those produced by the current method, regardless of coverage. June 2026 is the first month with data calculated for a specific date using the current method, which is why it was chosen as the base. Earlier months are excluded from the index series.
  • How we calculate the overall typical price — the typical price per m² is a weighted average of city medians, with each city’s weight proportional to its number of active listings. The same rule is applied separately to the resort group.
  • Active-property counts are a snapshot, not a trend — the active-property count in each edition reflects the situation on the calculation date. It is not used for comparisons between months because it is affected by our crawl coverage, rather than necessarily reflecting actual supply. We therefore publish only the count as of a specific date, without a change from the previous month.
  • Rules for changes to the index — a published index edition is never recalculated retroactively using new data. The composition of either group of locations changes only after an explicit announcement documented on this page.

We do not currently compare the index with the same month of the previous year because the history since June 2026 is still too short for a reliable annual comparison. We will add this comparison as soon as there is enough historical data.

Limitations

These limitations are inherent in the source data:

  • Asking prices, not transaction prices — we measure what sellers want, not what deals close at. When the market cools, asking prices lag actual ones by months.
  • "Off the market" never means "sold" — when a listing disappears, we know only that it is no longer published. The property may have been sold, or the listing may have been withdrawn, expired or moved elsewhere. We never call a property “sold” — that is a fact our data cannot establish.
  • Coverage is not the whole market — properties sold without a listing — between acquaintances, through a single broker, or before publication — are not included. In new developments a share of sales never reaches a portal at all.
  • AI enrichment can be wrong — property type and attributes are identified automatically, and summaries are generated from the listing’s text and photos. Where the listing is inaccurate or incomplete, the error carries through.
  • Period comparisons depend on the mix of properties — a quarter-on-quarter change reflects which properties are currently on offer, not only a change in the price of the same property. We therefore show a trend only when the sample is sufficient in both periods.

What AI does and does not do here

AI writes text. It summarises the listing description, extracts pros and cons and identifies which way the property faces. All generated content carries an "AI summary" label so you can recognise it.

AI does not calculate any figures. Medians, percentiles, differences from neighbourhood prices, yield and price history are calculated programmatically using the collected data and the rules described above. If we cannot justify a value using the methodology on this page, we do not publish it.

Citation and reuse

The data may be freely cited — by journalists, analysts, students and researchers — with attribution and a link to the specific page the figure came from.

Please do not present our figures as completed-transaction prices, and please state the date they apply to: the market pages are recalculated every four hours.

Example citation

imotesa.bg, “Average prices for apartments for sale in Sofia”, data as of 17 November 2026, https://www.imotesa.bg/statistics/sale/apartment/sofiya

Questions about the methodology, or requests for a breakdown that is not published: support@imotesa.com

Methodology last revised: August 2026