biztrac. BETA
COMPANY REGISTER PROFILE
834270862 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

K 40 EIENDOM AS

Org. no. 834270862 Limited company (AS) Ullensaker Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 276,000
Equity NOK 626,000
Incorporated 2024
Share capital NOK 600,000

K 40 EIENDOM AS is registered as a limited company in Ullensaker, Akershus with organisation number 834270862. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 600,000, divided into 1200 shares. The company's stated purpose is: “Selskapet driver med kjøp, utvikling, utleie og salg av fast eiendom og alt som hermed står i forbindelse med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 276,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 276,000
▲ +540 %
Equity
NOK 626,000
▲ +23 %
Est. value
NOK 827,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
12.7%
Good
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns K 40 EIENDOM AS?

K 40 EIENDOM AS
NOK 1.2m rev. · NOK 276,000 profit

K 40 EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about K 40 EIENDOM AS

Who owns K 40 EIENDOM AS?

Fredrik Vollebæk is the largest registered owner, with 50.0%.

What is the revenue of K 40 EIENDOM AS?

K 40 EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of K 40 EIENDOM AS?

Fredrik Vollebæk is registered as general manager of K 40 EIENDOM AS.

Where is K 40 EIENDOM AS based?

K 40 EIENDOM AS has its business address in Algarheim.

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.