BIZTRAC BETA
Uoppgitt

LELU INVEST AS

Org. no. 925144789 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 4.8m
Incorporated 2020
Share capital NOK 30,000

Signals

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

LELU INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 925144789. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 4.8m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns LELU INVEST AS?

TOR ANDRE LØBERG
LELU INVEST AS
NOK 0 rev. · NOK −6,000 profit

LELU INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LELU INVEST AS own?

LELU INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LELU INVEST AS

Who owns LELU INVEST AS?

TOR ANDRE LØBERG is the largest registered owner, with 100.0%.

What is the revenue of LELU INVEST AS?

LELU INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of LELU INVEST AS?

Tor Andre Løberg is registered as general manager of LELU INVEST AS.

Where is LELU INVEST AS based?

LELU INVEST AS has its business address in Nyborg.

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.