BIZTRAC BETA
Rental and operating of own or leased real estate

SKIPPERGATEN 59 AS

Org. no. 913442237 Limited company (AS) Kristiansand Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 4.3m
Equity NOK 19.6m
Incorporated 2014
Share capital NOK 650,000

SKIPPERGATEN 59 AS is registered as a limited company in Kristiansand, Agder with organisation number 913442237. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 650,000, divided into 1000 shares. The company's stated purpose is: “Eie, utleie og forvaltning av fast eiendom samt investering i aksjer og alt som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 4.3m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 4.3m
Equity
NOK 19.6m
Est. value
NOK 20.4m

Financial health · 2024

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

Who owns SKIPPERGATEN 59 AS?

KLEMENTIN EIENDOM AS
SKIPPERGATEN 59 AS
NOK 5.2m rev. · NOK 4.3m profit

SKIPPERGATEN 59 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SKIPPERGATEN 59 AS er morselskap for 5 datterselskaper:

Frequently asked questions about SKIPPERGATEN 59 AS

Who owns SKIPPERGATEN 59 AS?

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

What is the revenue of SKIPPERGATEN 59 AS?

SKIPPERGATEN 59 AS had revenue of NOK 5.2m in 2024.

Who is the general manager of SKIPPERGATEN 59 AS?

Jørgen Brøvig is registered as general manager of SKIPPERGATEN 59 AS.

Where is SKIPPERGATEN 59 AS based?

SKIPPERGATEN 59 AS has its business address in Kristiansand S.

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.