BIZTRAC BETA
Other captive investment companies

UNGEMOEN AS

Org. no. 821615402 Limited company (AS) Heim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK −339,000
Incorporated 2018
Share capital NOK 530,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−339k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

UNGEMOEN AS is registered as a limited company in Heim, Trøndelag with organisation number 821615402. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 530,000, divided into 530 shares. The company's stated purpose is: “Eie og forvalte finansielle aktiva som aksjer og verdipapirer, samt andre formuesverdier av hvilken som helst art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK −339,000

Financial health · 2024

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

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

Who owns UNGEMOEN AS?

Gaute Jømne Moen
UNGEMOEN AS
NOK 0 rev. · NOK −23,000 profit

UNGEMOEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UNGEMOEN AS own?

UNGEMOEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UNGEMOEN AS

Who owns UNGEMOEN AS?

Gaute Jømne Moen is the largest registered owner, with 100.0%.

What is the revenue of UNGEMOEN AS?

UNGEMOEN AS had revenue of NOK 0 in 2024.

Where is UNGEMOEN AS based?

UNGEMOEN AS has its business address in Halsanaustan.

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.