biztrac. BETA
COMPANY REGISTER PROFILE
918043799 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

KLEVER EIENDOM AS

Org. no. 918043799 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 4.4m
Equity NOK 507,000
Incorporated 2016
Share capital NOK 30,000

KLEVER EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 918043799. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 4.4m in operating profit.

Former names: ELAPHUS 12 AS

Key figures · 2025

Revenue
NOK 9.4m
▲ +3 %
Operating profit
NOK 4.4m
▼ −2 %
Equity
NOK 507,000
▲ +0 %
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
7.2%
Satisfactory
Return on total assets
Solidity
0.8%
Not satisfactory
Equity as a share of total capital

Who owns KLEVER EIENDOM AS?

KLEVER EIENDOM AS
NOK 9.4m rev. · NOK 4.4m profit

KLEVER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KLEVER EIENDOM AS

Who owns KLEVER EIENDOM AS?

SKEDSMOKORSET EIENDOMSUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of KLEVER EIENDOM AS?

KLEVER EIENDOM AS had revenue of NOK 9.4m in 2025.

Who is the general manager of KLEVER EIENDOM AS?

Dag William Bastiansen is registered as general manager of KLEVER EIENDOM AS.

Where is KLEVER EIENDOM AS based?

KLEVER EIENDOM AS has its business address in Oslo.

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.