BIZTRAC BETA
Rental and operating of own or leased real estate

KONGENSGATE 66 OG 68 AS

Org. no. 996981576 Limited company (AS) Kristiansand Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 1.5m
Equity NOK 7.8m
Incorporated 2011
Share capital NOK 2.3m

KONGENSGATE 66 OG 68 AS is registered as a limited company in Kristiansand, Agder with organisation number 996981576. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 2.3m, divided into 2275000 shares. The company's stated purpose is: “Eie, leie ut og drifte fast eiendom, og annet som står i naturlig forbindelse med dette - herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 1.5m
Equity
NOK 7.8m
Est. value
NOK 7.1m

Financial health · 2024

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

Who owns KONGENSGATE 66 OG 68 AS?

SVENDSENGRUPPEN AS
KONGENSGATE 66 OG 68 AS
NOK 2.7m rev. · NOK 1.5m profit

KONGENSGATE 66 OG 68 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGENSGATE 66 OG 68 AS

Who owns KONGENSGATE 66 OG 68 AS?

SVENDSENGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of KONGENSGATE 66 OG 68 AS?

KONGENSGATE 66 OG 68 AS had revenue of NOK 2.7m in 2024.

Who is the general manager of KONGENSGATE 66 OG 68 AS?

Daniel Svendsen is registered as general manager of KONGENSGATE 66 OG 68 AS.

Where is KONGENSGATE 66 OG 68 AS based?

KONGENSGATE 66 OG 68 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.