BIZTRAC BETA
Rental and operating of own or leased real estate

SJØGATA 42 AS

Org. no. 917873658 Limited company (AS) Tromsø Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 8.2m
Operating profit NOK 6.8m
Equity NOK 50.1m
Incorporated 2016
Share capital NOK 24.5m

Signals

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

SJØGATA 42 AS is registered as a limited company in Tromsø, Troms with organisation number 917873658. 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 24.5m, divided into 102 shares. The company's stated purpose is: “Eie, kjøpe, selge og leie ut fast eiendom, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.2m in revenue and NOK 6.8m in operating profit.

Key figures · 2025

Revenue
NOK 8.2m
Operating profit
NOK 6.8m
Equity
NOK 50.1m
Est. value
NOK 47.5m

Financial health · 2025

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

Who owns SJØGATA 42 AS?

COOP NORD SA
SJØGATA 42 AS
NOK 8.2m rev. · NOK 6.8m profit

SJØGATA 42 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SJØGATA 42 AS

Who owns SJØGATA 42 AS?

COOP NORD SA is the largest registered owner, with 100.0%.

What is the revenue of SJØGATA 42 AS?

SJØGATA 42 AS had revenue of NOK 8.2m in 2025.

Who is the general manager of SJØGATA 42 AS?

Pål Kristian Wilhelmsen is registered as general manager of SJØGATA 42 AS.

Where is SJØGATA 42 AS based?

SJØGATA 42 AS has its business address in Tromsø.

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.