BIZTRAC BETA
Development of building projects

LYKKEBERG BOLIGFELT BØ AS

Org. no. 928354113 Limited company (AS) Midt-Telemark Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK −688,000
Incorporated 2021
Share capital NOK 1.0m

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−688k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−24k kr).

LYKKEBERG BOLIGFELT BØ AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 928354113. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp av faste eiendommer for å utvikle tomtefelt med nødvendig infrastruktur for salg av boligtomter, samt investere i andre selskaper eller foreta andre investere.”.

Key figures · 2025

Operating profit
NOK −24,000
Equity
NOK −688,000

Financial health · 2025

Liquidity
397.51
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.1%
Weak
Equity as a share of total capital

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

Who owns LYKKEBERG BOLIGFELT BØ AS?

OPPHEIMJORDET UTVIKLING AS
LYKKEBERG BOLIGFELT BØ AS
· NOK −24,000 profit

LYKKEBERG BOLIGFELT BØ AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYKKEBERG BOLIGFELT BØ AS

Who owns LYKKEBERG BOLIGFELT BØ AS?

OPPHEIMJORDET UTVIKLING AS is the largest registered owner, with 33.4%.

Who is the general manager of LYKKEBERG BOLIGFELT BØ AS?

Einar Forberg is registered as general manager of LYKKEBERG BOLIGFELT BØ AS.

Where is LYKKEBERG BOLIGFELT BØ AS based?

LYKKEBERG BOLIGFELT BØ AS has its business address in Bø I Telemark.

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.