BIZTRAC BETA
Rental and operating of own or leased real estate

OSCARS GATE 52 AS

Org. no. 921694199 Limited company (AS) Arendal Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 378,000
Equity NOK 9.1m
Incorporated 2018
Share capital NOK 2.8m

Signals

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

OSCARS GATE 52 AS is registered as a limited company in Arendal, Agder with organisation number 921694199. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 2.8m, divided into 3000 shares. The company's stated purpose is: “Erverv, drift og utleie av eiendommer, samt alt som dermed står i forbindelse. Videre gjennom eierinteresser å delta i andre selskaper som har eiendomsdrift eller annen forretningsvirksomhet som formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 378,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 378,000
Equity
NOK 9.1m
Est. value
NOK 7.5m

Financial health · 2024

Liquidity
2.07
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
86.8%
Very good
Equity as a share of total capital

Who owns OSCARS GATE 52 AS?

SØRCO EIENDOM AS
OSCARS GATE 52 AS
NOK 1.7m rev. · NOK 378,000 profit

OSCARS GATE 52 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSCARS GATE 52 AS

Who owns OSCARS GATE 52 AS?

SØRCO EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of OSCARS GATE 52 AS?

OSCARS GATE 52 AS had revenue of NOK 1.7m in 2024.

Where is OSCARS GATE 52 AS based?

OSCARS GATE 52 AS has its business address in Arendal.

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.