BIZTRAC BETA
COMPANY REGISTER PROFILE
934390679 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

KVA EIENDOM AS

Org. no. 934390679 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

KVA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 934390679. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie, forvaltning og utvikling av fast eiendom, samt annen virksomhet som står i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2025

Liquidity
5.39
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
81.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KVA EIENDOM AS?

KVA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVA EIENDOM AS

Who owns KVA EIENDOM AS?

KV CONSULTING AS is the largest registered owner, with 100.0%.

Where is KVA EIENDOM AS based?

KVA EIENDOM AS has its business address in Oslo.

Property

Business address c/o Knut Valle Arnljot Gellines vei 5A, 0657 Oslo
Cadastral unit 301-236/1/0/0
Building Stort frittliggende boligbygg på 5 etg el mer · 47 units

17 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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