BIZTRAC BETA
COMPANY REGISTER PROFILE
986837353 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LEANGLIA AS

Org. no. 986837353 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 125,000
Incorporated 2004
Share capital NOK 108,000

Signals

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

LEANGLIA AS is registered as a limited company in Oslo, Oslo with organisation number 986837353. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2004. Registered share capital is NOK 108,000, divided into 108000 shares. The company's stated purpose is: “Å utvikle og selge eiendom, herunder overtagelse og videreutvikling av prosjektet Leanglia.”.

Key figures · 2025

Operating profit
NOK −4,000
▼ −114 %
Equity
NOK 125,000
▼ −2 %
Est. value
NOK 114,000

Financial health · 2025

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

Who owns LEANGLIA AS?

LEANGLIA AS has 12 registered shareholders:

All shareholders and roles →

Frequently asked questions about LEANGLIA AS

Who owns LEANGLIA AS?

ANDERS EIDE is the largest registered owner, with 47.0%.

Where is LEANGLIA AS based?

LEANGLIA AS has its business address in Oslo.

Property

Business address c/o SANDS Cort Adelers gate 33, 0254 Oslo
Cadastral unit 301-209/22/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

33 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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