BIZTRAC BETA
Rental and operating of own or leased real estate

LANGGATA 87 AS

Org. no. 830009922 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −427,000
Equity NOK −3.8m
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,8 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−427k kr).
  • Nylig endring 2026-06-08 Adresseendring registrert 2026-06-08.

LANGGATA 87 AS is registered as a limited company in Oslo, Oslo with organisation number 830009922. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom, utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2025

Operating profit
NOK −427,000
Equity
NOK −3.8m

Financial health · 2025

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

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

Who owns LANGGATA 87 AS?

ASSET 4 AS
LANGGATA 87 AS
· NOK −427,000 profit

LANGGATA 87 AS has 6 registered shareholders:

All shareholders and roles →

Group structure

LANGGATA 87 AS er morselskap for 3 datterselskaper:

Frequently asked questions about LANGGATA 87 AS

Who owns LANGGATA 87 AS?

ASSET 4 AS is the largest registered owner, with 50.1%.

Who is the general manager of LANGGATA 87 AS?

Marius Eide Wrengbro is registered as general manager of LANGGATA 87 AS.

Where is LANGGATA 87 AS based?

LANGGATA 87 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 15.06.2026.

Report a problem

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