BIZTRAC BETA
Uoppgitt

THONHAUGEN HOLDING AS

Org. no. 927323486 Limited company (AS) Enebakk Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK −12,000
Incorporated 2021
Share capital NOK 60,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−12k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-04-08 Aksjekapital registrert 2026-04-08.

THONHAUGEN HOLDING AS is registered as a limited company in Enebakk, Akershus with organisation number 927323486. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 6000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −5,000
Equity
NOK −12,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

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

Who owns THONHAUGEN HOLDING AS?

Anniken Thonhaugen
THONHAUGEN HOLDING AS
· NOK −5,000 profit

THONHAUGEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THONHAUGEN HOLDING AS own?

THONHAUGEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about THONHAUGEN HOLDING AS

Who owns THONHAUGEN HOLDING AS?

Anniken Thonhaugen is the largest registered owner, with 100.0%.

Where is THONHAUGEN HOLDING AS based?

THONHAUGEN HOLDING AS has its business address in Ytre Enebakk.

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.