biztrac. BETA
COMPANY REGISTER PROFILE
929083989 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Temporary employment agency activities and other human resource provisions

KONGEPARKEN DRIFT AS

Org. no. 929083989 Limited company (AS) Gjesdal Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 16.2m
Operating profit NOK 600,000
Equity NOK 191,000
Incorporated 2022
Employees 310
Share capital NOK 30,000

KONGEPARKEN DRIFT AS is registered as a limited company in Gjesdal, Rogaland with organisation number 929083989. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2022 and has 310 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drifts- og service-virksomhet og annet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.2m in revenue and NOK 600,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.2m
▲ +15 %
Operating profit
NOK 600,000
▲ +2 %
Equity
NOK 191,000
▲ +0 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
22.0%
Very good
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Who owns KONGEPARKEN DRIFT AS?

KONGEPARKEN DRIFT AS
NOK 16.2m rev. · NOK 600,000 profit

KONGEPARKEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KONGEPARKEN DRIFT AS

Who owns KONGEPARKEN DRIFT AS?

ROGALAND FRITIDSPARK AS is the largest registered owner, with 100.0%.

What is the revenue of KONGEPARKEN DRIFT AS?

KONGEPARKEN DRIFT AS had revenue of NOK 16.2m in 2025.

Where is KONGEPARKEN DRIFT AS based?

KONGEPARKEN DRIFT AS has its business address in Ålgård.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.