BIZTRAC BETA
Rental and operating of own or leased real estate

SKIPPERGATA 23 AS

Org. no. 917425833 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 3.4m
Equity NOK 10.1m
Incorporated 2016
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.

SKIPPERGATA 23 AS is registered as a limited company in Oslo, Oslo with organisation number 917425833. 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 100,000, divided into 1000 shares. The company's stated purpose is: “Eie, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 3.4m
Equity
NOK 10.1m
Est. value
NOK 13.8m

Financial health · 2024

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

Who owns SKIPPERGATA 23 AS?

SKB EIENDOM AS
SKIPPERGATA 23 AS
NOK 4.9m rev. · NOK 3.4m profit

SKIPPERGATA 23 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKIPPERGATA 23 AS

Who owns SKIPPERGATA 23 AS?

SKB EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of SKIPPERGATA 23 AS?

SKIPPERGATA 23 AS had revenue of NOK 4.9m in 2024.

Who is the general manager of SKIPPERGATA 23 AS?

Erlend Garmann Tuntland is registered as general manager of SKIPPERGATA 23 AS.

Where is SKIPPERGATA 23 AS based?

SKIPPERGATA 23 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.