BIZTRAC BETA
Rental and operating of own or leased real estate

LILLEBY INVEST AS

Org. no. 913859650 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −48,000
Equity NOK 10.8m
Incorporated 2014
Share capital NOK 80,000

Signals

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

LILLEBY INVEST AS is registered as a limited company in Fredrikstad, Østfold with organisation number 913859650. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 80,000, divided into 30 shares. The company's stated purpose is: “Investerings- og utleievirksomhet generelt, herunder oppføring, kjøp, salg og utleie av fast eiendom, investering i og utleie av fritidsbåter og investering i andre selskaper, samt alt annet som står i forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −48,000
Equity
NOK 10.8m
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns LILLEBY INVEST AS?

CHARLOTTE GJULEM LILLEBY
LILLEBY INVEST AS
· NOK −48,000 profit

LILLEBY INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LILLEBY INVEST AS own?

LILLEBY INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LILLEBY INVEST AS

Who owns LILLEBY INVEST AS?

CHARLOTTE GJULEM LILLEBY is the largest registered owner, with 50.0%.

Who is the general manager of LILLEBY INVEST AS?

Svend Erik Lilleby is registered as general manager of LILLEBY INVEST AS.

Where is LILLEBY INVEST AS based?

LILLEBY 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.