BIZTRAC BETA
Landscape service activities

IMAGO AS

Org. no. 930796115 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 15,000
Operating profit NOK −35,000
Equity NOK −34,000
Incorporated 2023
Share capital NOK 50,000

Signals

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

IMAGO AS is registered as a limited company in Oslo, Oslo with organisation number 930796115. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2023. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Selge tjenester og varer innen plantevitenskap - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 15,000 in revenue and NOK −35,000 in operating profit.

Key figures · 2024

Revenue
NOK 15,000
Operating profit
NOK −35,000
Equity
NOK −34,000

Financial health · 2024

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

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

Who owns IMAGO AS?

Even Klyve-Dahl
IMAGO AS
NOK 15,000 rev. · NOK −35,000 profit

IMAGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about IMAGO AS

Who owns IMAGO AS?

Even Klyve-Dahl is the largest registered owner, with 100.0%.

What is the revenue of IMAGO AS?

IMAGO AS had revenue of NOK 15,000 in 2024.

Who is the general manager of IMAGO AS?

Even Klyve-Dahl is registered as general manager of IMAGO AS.

Where is IMAGO AS based?

IMAGO 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 15.06.2026.

Report a problem

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