biztrac. BETA
COMPANY REGISTER PROFILE
913278135 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

LILLEAKER BOLIGUTVIKLING AS

Org. no. 913278135 Limited company (AS) Oslo Incorporated 2014 Active
Operating profit NOK −210,000
Equity NOK −164,000
Incorporated 2014
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−164k kr).

LILLEAKER BOLIGUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 913278135. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Erverve, utvikle, drive og avhende fast eiendom, samt all annen naturlig tilhørende virksomhet. Selskapet kan eie aksjer i andre selskaper.”.

Former names: PRO L AS

Key figures · 2025

Operating profit
NOK −210,000
▲ +91 %
Equity
NOK −164,000
▲ +91 %

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-107.8%
Weak
Equity as a share of total capital

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

Who owns LILLEAKER BOLIGUTVIKLING AS?

LILLEAKER BOLIGUTVIKLING AS
· NOK −210,000 profit

LILLEAKER BOLIGUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LILLEAKER BOLIGUTVIKLING AS

Who owns LILLEAKER BOLIGUTVIKLING AS?

GJELSTEN BOLIG AS is the largest registered owner, with 50.0%.

Who is the general manager of LILLEAKER BOLIGUTVIKLING AS?

Jon Lerstang is registered as general manager of LILLEAKER BOLIGUTVIKLING AS.

Where is LILLEAKER BOLIGUTVIKLING AS based?

LILLEAKER BOLIGUTVIKLING AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.