BIZTRAC BETA
Rental and operating of own or leased real estate

GRØNLANDSLEIRET 39 EIENDOM 3 AS

Org. no. 999247628 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 375,000
Operating profit NOK 109,000
Equity NOK 431,000
Incorporated 2012
Share capital NOK 168,000

GRØNLANDSLEIRET 39 EIENDOM 3 AS is registered as a limited company in Oslo, Oslo with organisation number 999247628. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 168,000, divided into 1680 shares. The company's stated purpose is: “Fast eiendom, herunder å eie, drive og selge fast eiendom, samt annen virksomhet som naturlig faller inn under denne beskrivelsen.”. The most recent filed accounts, for the 2024 financial year, show NOK 375,000 in revenue and NOK 109,000 in operating profit.

Key figures · 2024

Revenue
NOK 375,000
Operating profit
NOK 109,000
Equity
NOK 431,000
Est. value
NOK 483,000

Financial health · 2024

Liquidity
0.25
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.0%
Good
Equity as a share of total capital

Who owns GRØNLANDSLEIRET 39 EIENDOM 3 AS?

GRØNLANDSLEIRET 39 EIENDOM 8 AS
GRØNLANDSLEIRET 39 EIENDOM 3 AS
NOK 375,000 rev. · NOK 109,000 profit

GRØNLANDSLEIRET 39 EIENDOM 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRØNLANDSLEIRET 39 EIENDOM 3 AS

Who owns GRØNLANDSLEIRET 39 EIENDOM 3 AS?

GRØNLANDSLEIRET 39 EIENDOM 8 AS is the largest registered owner, with 100.0%.

What is the revenue of GRØNLANDSLEIRET 39 EIENDOM 3 AS?

GRØNLANDSLEIRET 39 EIENDOM 3 AS had revenue of NOK 375,000 in 2024.

Where is GRØNLANDSLEIRET 39 EIENDOM 3 AS based?

GRØNLANDSLEIRET 39 EIENDOM 3 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.