biztrac. BETA
COMPANY REGISTER PROFILE
929578872 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

COLPARK 5 AS

Org. no. 929578872 Limited company (AS) Kongsvinger Incorporated 2022 Active
Revenue 2025 NOK 105,000
Operating profit NOK −56,000
Equity NOK 177,000
Incorporated 2022
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−56k kr).

COLPARK 5 AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 929578872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer, eiendom og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 105,000 in revenue and NOK −56,000 in operating profit.

Former names: NYE COLPARK 5 AS

Key figures · 2025

Revenue
NOK 105,000
▼ −97 %
Operating profit
NOK −56,000
▼ −102 %
Equity
NOK 177,000
▼ −62 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
3.8%
Weak
Equity as a share of total capital

Who owns COLPARK 5 AS?

COLPARK 5 AS
NOK 105,000 rev. · NOK −56,000 profit

COLPARK 5 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

COLPARK 5 AS er morselskap for 2 datterselskaper:

Frequently asked questions about COLPARK 5 AS

Who owns COLPARK 5 AS?

TAURUS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of COLPARK 5 AS?

COLPARK 5 AS had revenue of NOK 105,000 in 2025.

Where is COLPARK 5 AS based?

COLPARK 5 AS has its business address in Kongsvinger.

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.