č.ev. 23, 410 02 Evaň

Jiná stavba · Evaň · Ústecký kraj

RÚIAN code120949806
IDc75209f2
Updated30 September 2026

Summary

Jiná stavba at č.ev. 23, 410 02 Evaň, Ústecký kraj. Built in 1976, has 2 floors, underground included, covers 22 m² of ground, its usable floor area is 37 m². Dwellings: 0. Its building code in RÚIAN, the Czech register of addresses and buildings, is 120949806.

Year built: 1976
Floors (incl. underground): 2
Footprint area (m²): 22
Height (m): unknown

~ estimate · “unknown”: in no record of the building

Building

Use: Jiná stavba
Year built: 1976
Floors (incl. underground): 2
Dwellings: 0
Usable floor area (m²): 37
Building code (RÚIAN): 120949806
Building ID: c75209f2-8287-4c2d-9eab-fed14fbc4510
Updated: 30 September 2026

Shape and roof

Footprint area (m²): 22
Height (m): unknown
Volume (m³): unknown
Roof shape: unknown

Outline · seen from above, north up

Risks

Flood zone: outside mapped flood zones

Location

The building and its neighbours · seen from above, north up this building other buildings

Street: unknown
Number: č.ev. 23
Municipality: Evaň
Region: Ústecký kraj
Postcode: 410 02
Coordinates (lat, lon): 50.38909, 14.03493
Buildings on the street: unknown

Companies and solar panels

Companies registered at this address: none found
Solar panel check: not checked yet

Company names, the solar panel check on dated imagery and export are in the app.

Nearby

Buildings nearby

Address	Built	Floors	Distance
č.ev. 22, 410 02 Evaň 1976 · 2 floors	1976	2 floors	12 m
č.ev. 17, 410 02 Evaň 2016 · 2 floors	2016	2 floors	27 m
č.ev. 11, 410 02 Evaň 1989 · 1 floor	1989	1 floor	49 m
č.ev. 18, 410 02 Evaň 2019 · 2 floors	2019	2 floors	59 m
č.ev. 20, 410 02 Evaň 1976 · 2 floors	1976	2 floors	80 m
č.ev. 19, 410 02 Evaň 1991 · 1 floor	1991	1 floor	158 m
č.p. 128, 410 02 Evaň 1946–1960 · 1 floor	1946–1960	1 floor	196 m
č.p. 32, 410 02 Evaň before 1920 · 1 floor	before 1920	1 floor	211 m
č.p. 142, 410 02 Evaň 2011 · 2 floors	2011	2 floors	391 m
č.ev. 16, 410 02 Evaň 2014 · 1 floor	2014	1 floor	426 m
č.p. 133, 410 02 Evaň 1920–1945 · 1 floor	1920–1945	1 floor	443 m
č.p. 113, 410 02 Evaň 1920–1945 · 1 floor	1920–1945	1 floor	474 m
č.p. 68, 410 02 Evaň 1981–1990 · 1 floor	1981–1990	1 floor	507 m
č.ev. 10, 410 02 Evaň 1976 · 2 floors	1976	2 floors	512 m
č.p. 70, 410 02 Evaň 1981–1990 · 1 floor	1981–1990	1 floor	514 m
č.p. 11, 410 02 Evaň 1991–2000 · 2 floors	1991–2000	2 floors	533 m
č.p. 12, 410 02 Evaň 1981–1990 · 1 floor	1981–1990	1 floor	535 m
č.p. 85, 410 02 Evaň 1946–1960 · 2 floors	1946–1960	2 floors	538 m
č.p. 82, 410 02 Evaň 1898 · 2 floors	1898	2 floors	539 m
č.p. 40, 410 02 Evaň 1971–1980 · 1 floor	1971–1980	1 floor	547 m

Questions

When was the building at Evaň č.ev. 23 built?

The building at Evaň č.ev. 23 was completed in 1976.

How many floors does the building at Evaň č.ev. 23 have?

The building at Evaň č.ev. 23 has 2 floors, underground included.

What is the RÚIAN building code of Evaň č.ev. 23?

The building’s code in RÚIAN, the Czech register of addresses and buildings, is 120949806. The official record opens from the “Building” table.

The same data, from your AI assistant or the API

Connect baseray to ChatGPT or Claude and ask about any building in Romania and Czechia, or read its record from your own code.

AI assistant

Ask, for example:

What do you know about the building at Evaň č.ev. 23? Which companies are registered there?

Connect ChatGPT or Claude

API

This building’s record as JSON:

curl "https://api.baseray.ai/v1/buildings/c75209f2-8287-4c2d-9eab-fed14fbc4510" \
  -H "Authorization: Bearer $BASERAY_API_KEY"

const response = await fetch("https://api.baseray.ai/v1/buildings/c75209f2-8287-4c2d-9eab-fed14fbc4510", {
  headers: { Authorization: `Bearer ${process.env.BASERAY_API_KEY}` },
});
const building = await response.json();

import os
import requests

response = requests.get(
    "https://api.baseray.ai/v1/buildings/c75209f2-8287-4c2d-9eab-fed14fbc4510",
    headers={"Authorization": f"Bearer {os.environ['BASERAY_API_KEY']}"},
    timeout=30,
)
building = response.json()

Create an API key API documentation