BIZTRAC BETA
Construction of residential and non-residential buildings

ALTENBURG HOLDING AS

Org. no. 989258125 Limited company (AS) Skien Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −77,000
Equity NOK 10.4m
Incorporated 2005
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−77k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ALTENBURG HOLDING AS is registered as a limited company in Skien, Telemark with organisation number 989258125. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Eie fast eiendom, eiendomsutvikling og utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt anne virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −77,000
Equity
NOK 10.4m
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns ALTENBURG HOLDING AS?

PER ØYVIND BLEGEN LAURITSEN
ALTENBURG HOLDING AS
· NOK −77,000 profit

ALTENBURG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ALTENBURG HOLDING AS own?

ALTENBURG HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ALTENBURG HOLDING AS

Who owns ALTENBURG HOLDING AS?

PER ØYVIND BLEGEN LAURITSEN is the largest registered owner, with 100.0%.

Where is ALTENBURG HOLDING AS based?

ALTENBURG HOLDING AS has its business address in Skien.

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.