BIZTRAC BETA
Development of building projects

TELEMARK LAGERPARK AS

Org. no. 828335022 Limited company (AS) Notodden Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 27.1m
Operating profit NOK 5.7m
Equity NOK 481,000
Incorporated 2021
Share capital NOK 100,000

TELEMARK LAGERPARK AS is registered as a limited company in Notodden, Telemark with organisation number 828335022. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av fast eiendom og hva som står i en naturlig tilknytting til dette. Selskapet kan eie aksjer/andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.1m in revenue and NOK 5.7m in operating profit.

Key figures · 2024

Revenue
NOK 27.1m
Operating profit
NOK 5.7m
Equity
NOK 481,000
Est. value
NOK 14.2m

Financial health · 2024

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

Who owns TELEMARK LAGERPARK AS?

SPERRE GROUP AS
TELEMARK LAGERPARK AS
NOK 27.1m rev. · NOK 5.7m profit

TELEMARK LAGERPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TELEMARK LAGERPARK AS

Who owns TELEMARK LAGERPARK AS?

SPERRE GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of TELEMARK LAGERPARK AS?

TELEMARK LAGERPARK AS had revenue of NOK 27.1m in 2024.

Who is the general manager of TELEMARK LAGERPARK AS?

Thor Olav Eikeland Sperre is registered as general manager of TELEMARK LAGERPARK AS.

Where is TELEMARK LAGERPARK AS based?

TELEMARK LAGERPARK AS has its business address in Notodden.

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.