RU Cadastral Object Lookup (Rosreestr/NSPD)
Pricing
from $50.00 / 1,000 object looked ups
RU Cadastral Object Lookup (Rosreestr/NSPD)
Look up a real estate object on the Russian cadastral map (NSPD, Rosreestr) by cadastral number or address, no captcha. Returns object type, address, area, purpose, status, cadastral value and ownership form. Does not return owner name or right registration date, both captcha gated.
Pricing
from $50.00 / 1,000 object looked ups
Rating
0.0
(0)
Developer
Ivan Solovyev
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
🗺️ RU Cadastral Object Lookup (Rosreestr / NSPD)
|
What is this property, by cadastral number or address? Look up any Russian real estate object on the public cadastral map: type, address, area, purpose, status, cadastral value with its revaluation dates, ownership form, map coordinates, and what the object consists of. Open cadastral data, no official extract required. |
|
🗺️ Object card Type, address, area, purpose and status by cadastral number or address |
💰 Cadastral value Current value together with its revaluation dates |
📍 Coordinates and composition Outline and centre on the map, premises inside a building, objects on a parcel |
🚧 Restrictions and zones Protected-use zones, territorial zones and heritage territories covering the object |
Look up a Russian real estate object on the public cadastral map - NSPD (Национальная система пространственных данных, Rosreestr's open geoportal) - by cadastral number (exact match) or address (free text).
Returns the object's open cadastral card: object type (land parcel / building / structure / premises), address, area, purpose, permitted use, status, cadastral value with its revaluation dates, ownership-form category (state/municipal/private, when NSPD has it on file), and physical attributes (floors, wall material, year built, parent building for premises, etc).
Every card also carries where the object is and what it consists of: the outline in GeoJSON and WGS84 with a centre point and bounding box, the premises and parking spaces registered inside a building, the objects standing on a land parcel, the parcel a building sits on, registered parts, and single-land-use composition.
Scope
Owner name and right/ownership registration date are not included - a full ЕГРН extract is
required for that and is out of scope for this actor. The cadastralRegistrationDate field is the
date the object was assigned its cadastral number, a separate, one-time event.
Modes
- search - one card per query in
queries. An exact cadastral number (e.g.77:01:0001005:1026) always returns the one matching object. An address returns up tomaxResultsmatches, in NSPD's own relevance order. - monitor - run on a schedule; compares against the previous run's snapshot (Key-Value Store,
keyed by cadastral number) and emits only objects that actually changed, each with a
changeNotedescribing what changed. Tracked: cadastral value, status, area, removal from the register, and the composition itself, so a new unit registered inside a building or a new building on a parcel raises a signal on its own. Optionally POSTs a summary tonotifyWebhookUrl(wire it to n8n/Zapier/Make for Telegram/Slack alerts).
Composition and links
A cadastral card on its own answers "what is this object". These fields answer "what is inside it and what is it attached to", which is what turns a single lookup into a picture of a site:
| Field | What it answers |
|---|---|
premisesCount, parkingCount | How many premises and parking spaces are registered inside a building |
premisesCadNumbers | Their cadastral numbers, ready to look up in turn |
objectsOnLand | Everything standing on a land parcel |
landCadNumbers | The parcel a building or structure is located within |
landParts, buildingParts | Registered parts, the ones an encumbrance is recorded against |
landUseComposition | Parcels making up a single land use |
intersectedCadNumbers, unitedCadNumbers | Objects overlapping or merged with this one |
One address query therefore expands into the full stack at that address: parcel, the buildings on it, and the units inside each building.
Restrictions and zones
Set includeZones and every object is checked against 13 restriction layers of the public
cadastral map. This is the part that decides what may actually be done with a plot, and it is
absent from a plain cadastral card:
| Group | Layers |
|---|---|
| Protected-use zones (ЗОУИТ) | cultural heritage, energy/communications/transport, nature, security and guarded facilities, other |
| Planning | territorial zones, red lines |
| Protected territories | heritage territories, protected natural areas, forestries, shorelines |
| Special regimes | special economic zones, priority development areas |
Each hit comes back with its layer, the boundary registry number (for example 77:01-7.6241) and
its type, in the zones array, with zoneCount alongside. Zero means checked and nothing found;
an empty field means the check was not run.
The check uses the object's own footprint rather than a single centre point, so a boundary crossing the edge of a large plot is still caught. It is one request per layer, which is why it is off by default.
Coordinates
centroid and bbox come with every record in plain WGS84 longitude and latitude, so a result
drops straight into a map, a geocoder or a distance calculation. geometry holds the full outline
as GeoJSON, geometryPoints tells you how detailed that outline is. Set includeGeometry to false
when you want the location but not the polygon.
Input
| Field | Description |
|---|---|
mode | search or monitor |
queries | Cadastral numbers or addresses to look up |
maxResults | Max matches to fetch per address query (ignored for exact cadastral numbers) |
includeComposition | Also resolve premises, objects on a parcel, the parcel under a building and registered parts (on by default) |
includeGeometry | Return the full outline; the centre point and bounding box are returned either way (on by default) |
includeZones | Check the object against 13 restriction and zoning layers (off by default) |
notifyWebhookUrl | Monitor mode: webhook for the run summary |
proxyConfiguration | Required on Apify: Apify Residential proxy, country RU. All sources require a Russian IP. |
The systemInfoUpdatedAt field
Every NSPD record carries an internal systemInfo.updated service timestamp, not part of the
public API contract and not shown in NSPD's own UI card. It changes whenever something in the
record changes - a cadastral-value revaluation, a boundary/attribute correction, or another update.
Monitor mode tracks it as an additional "something changed, go look" signal alongside
cadastralValue and status, and every monitor record's changeNote names what changed.
Output fields
See .actor/dataset_schema.json for the full, typed field list. Key ones: cadastralNumber,
objectType, address, area, purpose, permittedUse, status, ownershipType,
cadastralValue, costIndex, costRegistrationDate/costApplicationDate/costDeterminationDate
(revaluation dates), cadastralRegistrationDate (date of cadastral-number assignment), centroid
and bbox (WGS84), geometry (GeoJSON outline), premisesCadNumbers/objectsOnLand/
landCadNumbers (composition and links), zones and zoneCount (restrictions), isRemoved, and
url (link back to the object on the NSPD map, the source of every record).
RU: область применения
Актор собирает открытые кадастровые данные объекта недвижимости с публичной карты Росреестра (НСПД) - по кадастровому номеру (точное совпадение) или по адресу (список совпадений).
Актор не возвращает ФИО/наименование правообладателя и дату регистрации права собственности - для
этого нужна отдельная выписка ЕГРН, что выходит за рамки актора. Поле cadastralRegistrationDate -
это дата присвоения кадастрового номера объекту, отдельное разовое событие.
Поле systemInfoUpdatedAt - это служебный таймштамп НСПД (не часть публичного контракта API, не
показывается в самой карточке на сайте). Он меняется, когда в записи что-то поменялось: переоценка
кадастровой стоимости, уточнение границ/атрибутов или другое обновление. В режиме monitor это
дополнительный сигнал наряду с cadastralValue и status, а поле changeNote называет, что именно
изменилось.
Кроме самой карточки актор отдаёт координаты и состав объекта: контур в GeoJSON и WGS84 с центром и
габаритной рамкой, помещения и машино-места, учтённые в здании, объекты на земельном участке,
участок под зданием, учтённые части и состав единого землепользования. Один запрос по адресу таким
образом разворачивается в связку «участок, здания на нём, помещения внутри». В режиме monitor
изменение состава отслеживается наравне с кадастровой стоимостью: постановка нового помещения на
учёт или снятие объекта с учёта поднимают сигнал сами по себе.
По флагу includeZones объект дополнительно проверяется по тринадцати слоям ограничений публичной
кадастровой карты: зоны с особыми условиями использования (охрана памятников, энергетика и
транспорт, природные территории, охраняемые объекты, иные), территориальные зоны, красные линии,
территории объектов культурного наследия, ООПТ, лесничества, береговые линии, особые экономические
зоны и территории опережающего развития. Именно эти сведения решают, что на участке можно
построить, и в обычной кадастровой карточке их нет. Проверка идёт по контуру объекта, а не по одной
точке в центре, поэтому граница, задевающая край крупного участка, тоже попадает в ответ.
🔗 Все наши акторы для данных по России, Казахстану и СНГ
Одна линейка для маркетплейсов, госзакупок и проверки контрагентов - соседний актор открывается одним кликом по карточке.