BIZTRAC BETA
Rental and operating of own or leased real estate

ARBINSGATE 2 AS

Org. no. 919092742 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 6.3m
Equity NOK 15.5m
Incorporated 2016
Share capital NOK 6.1m

Signals

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

ARBINSGATE 2 AS is registered as a limited company in Oslo, Oslo with organisation number 919092742. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 6.1m, divided into 6149 shares. The company's stated purpose is: “Selskapets virksomhet er å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 6.3m in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 6.3m
Equity
NOK 15.5m
Est. value
NOK 22.0m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Good
Equity as a share of total capital

Who owns ARBINSGATE 2 AS?

MALLING CORE PLUS I HOLDING AS
ARBINSGATE 2 AS
NOK 9.5m rev. · NOK 6.3m profit

ARBINSGATE 2 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ARBINSGATE 2 AS er morselskap for 3 datterselskaper:

Frequently asked questions about ARBINSGATE 2 AS

Who owns ARBINSGATE 2 AS?

MALLING CORE PLUS I HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARBINSGATE 2 AS?

ARBINSGATE 2 AS had revenue of NOK 9.5m in 2024.

Where is ARBINSGATE 2 AS based?

ARBINSGATE 2 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.