BIZTRAC BETA
Other business support service activities n.e.c.

KLOKE HODER AS

Org. no. 920486525 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 6,000
Operating profit NOK −2.4m
Equity NOK 12.8m
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,4 mill kr).

KLOKE HODER AS is registered as a limited company in Stavanger, Rogaland with organisation number 920486525. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive forretningsstøtte gjennom konsulentvirksomhet og investeringer eller handel og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 6,000 in revenue and NOK −2.4m in operating profit.

Key figures · 2024

Revenue
NOK 6,000
Operating profit
NOK −2.4m
Equity
NOK 12.8m
Est. value
NOK 43.7m

Financial health · 2024

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

Who owns KLOKE HODER AS?

LEIV MIDTHASSEL
KLOKE HODER AS
NOK 6,000 rev. · NOK −2.4m profit

KLOKE HODER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KLOKE HODER AS own?

KLOKE HODER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KLOKE HODER AS

Who owns KLOKE HODER AS?

LEIV MIDTHASSEL is the largest registered owner, with 51.0%.

What is the revenue of KLOKE HODER AS?

KLOKE HODER AS had revenue of NOK 6,000 in 2024.

Where is KLOKE HODER AS based?

KLOKE HODER AS has its business address in Stavanger.

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

Report a problem

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