BIZTRAC BETA
Rental and operating of own or leased real estate

OPPSALSTUBBEN 3 AS

Org. no. 916239610 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 923,000
Equity NOK 3.9m
Incorporated 2015
Share capital NOK 500,000

Signals

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

OPPSALSTUBBEN 3 AS is registered as a limited company in Oslo, Oslo with organisation number 916239610. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 500,000, divided into 50000 shares. The company's stated purpose is: “Investering i eiendom og eiendomsrelaterte aksjer, samt virksomhet som har tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 923,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 923,000
Equity
NOK 3.9m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
0.06
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.5%
Satisfactory
Equity as a share of total capital

Who owns OPPSALSTUBBEN 3 AS?

NG EIENDOM ØST AS
OPPSALSTUBBEN 3 AS
NOK 2.4m rev. · NOK 923,000 profit

OPPSALSTUBBEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

OPPSALSTUBBEN 3 AS er morselskap for 249 datterselskaper:

Frequently asked questions about OPPSALSTUBBEN 3 AS

Who owns OPPSALSTUBBEN 3 AS?

NG EIENDOM ØST AS is the largest registered owner, with 100.0%.

What is the revenue of OPPSALSTUBBEN 3 AS?

OPPSALSTUBBEN 3 AS had revenue of NOK 2.4m in 2024.

Where is OPPSALSTUBBEN 3 AS based?

OPPSALSTUBBEN 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.