BIZTRAC BETA
Development of building projects

DAMLIVEGEN AS

Org. no. 933571718 Limited company (AS) Eidskog Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 11.9m
Operating profit NOK 2.0m
Equity NOK 283,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DAMLIVEGEN AS is registered as a limited company in Eidskog, Innlandet with organisation number 933571718. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Eiendomsutvikling og det som naturlig står i forbindelse med dette, herunder deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 11.9m
Operating profit
NOK 2.0m
Equity
NOK 283,000
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.6%
Not satisfactory
Equity as a share of total capital

Who owns DAMLIVEGEN AS?

Ø M FJELD UTVIKLING AS
DAMLIVEGEN AS
NOK 11.9m rev. · NOK 2.0m profit

DAMLIVEGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAMLIVEGEN AS

Who owns DAMLIVEGEN AS?

Ø M FJELD UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of DAMLIVEGEN AS?

DAMLIVEGEN AS had revenue of NOK 11.9m in 2025.

Who is the general manager of DAMLIVEGEN AS?

Tom Wiggo Bjerknes is registered as general manager of DAMLIVEGEN AS.

Where is DAMLIVEGEN AS based?

DAMLIVEGEN AS has its business address in Skotterud.

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.