BIZTRAC BETA
Rental and operating of own or leased real estate

LYKKEBERG EIENDOM AS

Org. no. 867534482 Limited company (AS) Fredrikstad Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 408,000
Operating profit NOK −58,000
Equity NOK 927,000
Incorporated 1993
Share capital NOK 102,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−58k kr).

LYKKEBERG EIENDOM AS is registered as a limited company in Fredrikstad, Østfold with organisation number 867534482. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Kjøp og salg, samt utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 408,000 in revenue and NOK −58,000 in operating profit.

Key figures · 2025

Revenue
NOK 408,000
Operating profit
NOK −58,000
Equity
NOK 927,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns LYKKEBERG EIENDOM AS?

PETER TRYGVE HANSEN
LYKKEBERG EIENDOM AS
NOK 408,000 rev. · NOK −58,000 profit

LYKKEBERG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYKKEBERG EIENDOM AS

Who owns LYKKEBERG EIENDOM AS?

PETER TRYGVE HANSEN is the largest registered owner, with 50.0%.

What is the revenue of LYKKEBERG EIENDOM AS?

LYKKEBERG EIENDOM AS had revenue of NOK 408,000 in 2025.

Who is the general manager of LYKKEBERG EIENDOM AS?

Peter Trygve Hansen is registered as general manager of LYKKEBERG EIENDOM AS.

Where is LYKKEBERG EIENDOM AS based?

LYKKEBERG EIENDOM AS has its business address in Fredrikstad.

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.