biztrac. BETA
COMPANY REGISTER PROFILE
912866017 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

KEVA EIENDOM AS

Org. no. 912866017 Limited company (AS) Bærum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 4.0m
Equity NOK 8.1m
Incorporated 2013
Share capital NOK 270,000

KEVA EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 912866017. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 270,000, divided into 67490 shares. The company's stated purpose is: “Kjøpe, selge, forvalte og bestyre fast eiendom og andre formuesverdier samt gjennom aksjeervervelse eller på annen måte gjøre seg interessert i selskaper av enhver art.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 4.0m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
▲ +898 %
Operating profit
NOK 4.0m
▲ +1455 %
Equity
NOK 8.1m
▲ +61 %
Est. value
NOK 11.7m

Financial health · 2025

Liquidity
19.61
Very good
Current assets ÷ current liabilities
Profitability
57.7%
Very good
Return on total assets
Solidity
86.7%
Very good
Equity as a share of total capital

Who owns KEVA EIENDOM AS?

KEVA EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KEVA EIENDOM AS own?

KEVA EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KEVA EIENDOM AS

Who owns KEVA EIENDOM AS?

Kirsten Elise Haraldson Vanberg is the largest registered owner, with 80.0%.

What is the revenue of KEVA EIENDOM AS?

KEVA EIENDOM AS had revenue of NOK 4.8m in 2025.

Where is KEVA EIENDOM AS based?

KEVA EIENDOM AS has its business address in Jar.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.