BIZTRAC BETA
Rental and operating of own or leased real estate

GREFSENVEIEN 61 AS

Org. no. 990309388 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 836,000
Equity NOK 3.5m
Incorporated 2006
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GREFSENVEIEN 61 AS is registered as a limited company in Oslo, Oslo with organisation number 990309388. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eie, utleie og utvikling av eiendom samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 836,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 836,000
Equity
NOK 3.5m
Est. value
NOK 3.6m

Financial health · 2024

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.7%
Good
Equity as a share of total capital

Who owns GREFSENVEIEN 61 AS?

LANIMA AS
GREFSENVEIEN 61 AS
NOK 1.9m rev. · NOK 836,000 profit

GREFSENVEIEN 61 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

GREFSENVEIEN 61 AS er morselskap for 5 datterselskaper:

Frequently asked questions about GREFSENVEIEN 61 AS

Who owns GREFSENVEIEN 61 AS?

LANIMA AS is the largest registered owner, with 100.0%.

What is the revenue of GREFSENVEIEN 61 AS?

GREFSENVEIEN 61 AS had revenue of NOK 1.9m in 2024.

Where is GREFSENVEIEN 61 AS based?

GREFSENVEIEN 61 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.