BIZTRAC BETA
Site preparation

LIEBEKK INVEST AS

Org. no. 929535502 Limited company (AS) Fredrikstad Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −99,000
Equity NOK 37.7m
Incorporated 2022
Share capital NOK 260,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−99k kr).

LIEBEKK INVEST AS is registered as a limited company in Fredrikstad, Østfold with organisation number 929535502. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 260,000, divided into 50 shares. The company's stated purpose is: “Å eie/investere i andre selskaper, herunder investering i aksjer, andeler i selskap etter selskapsloven, obligasjoner, fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −99,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −99,000
Equity
NOK 37.7m
Est. value
NOK 38.6m

Financial health · 2024

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

Who owns LIEBEKK INVEST AS?

DAGFINN LIE
LIEBEKK INVEST AS
NOK 0 rev. · NOK −99,000 profit

LIEBEKK INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LIEBEKK INVEST AS own?

LIEBEKK INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LIEBEKK INVEST AS

Who owns LIEBEKK INVEST AS?

DAGFINN LIE is the largest registered owner, with 30.0%.

What is the revenue of LIEBEKK INVEST AS?

LIEBEKK INVEST AS had revenue of NOK 0 in 2024.

Where is LIEBEKK INVEST AS based?

LIEBEKK INVEST AS has its business address in Gressvik.

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.