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

HASLE LINJE BYGG 01 EXIT AS

Org. no. 920623859 Limited company (AS) Oslo Incorporated 2018 Active
Operating profit NOK −207,000
Equity NOK −4.4m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,4 mill kr).

HASLE LINJE BYGG 01 EXIT AS is registered as a limited company in Oslo, Oslo with organisation number 920623859. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 100,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 65 AS

Key figures · 2025

Operating profit
NOK −207,000
▲ +30 %
Equity
NOK −4.4m
▼ −8 %

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
-117.7%
Not satisfactory
Return on total assets
Solidity
-3678.9%
Weak
Equity as a share of total capital

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

Who owns HASLE LINJE BYGG 01 EXIT AS?

HASLE LINJE BYGG 01 EXIT AS
· NOK −207,000 profit

HASLE LINJE BYGG 01 EXIT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HASLE LINJE BYGG 01 EXIT AS

Who owns HASLE LINJE BYGG 01 EXIT AS?

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

Who is the general manager of HASLE LINJE BYGG 01 EXIT AS?

Tone Irene Lindemark is registered as general manager of HASLE LINJE BYGG 01 EXIT AS.

Where is HASLE LINJE BYGG 01 EXIT AS based?

HASLE LINJE BYGG 01 EXIT 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.