BIZTRAC BETA
Uoppgitt

COLORTEC HOLDING AS

Org. no. 917091005 Limited company (AS) Fredrikstad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −21,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−21k kr).

COLORTEC HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 917091005. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer i aksjer, andeler og fast eiendom, samt alt som faller naturlig sammen med dette inkludert deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −21,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns COLORTEC HOLDING AS?

PÅL KENNETH MØKLEGÅRD
COLORTEC HOLDING AS
NOK 0 rev. · NOK 0 profit

COLORTEC HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COLORTEC HOLDING AS

Who owns COLORTEC HOLDING AS?

PÅL KENNETH MØKLEGÅRD is the largest registered owner, with 100.0%.

What is the revenue of COLORTEC HOLDING AS?

COLORTEC HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of COLORTEC HOLDING AS?

Pål Kenneth Møklegård is registered as general manager of COLORTEC HOLDING AS.

Where is COLORTEC HOLDING AS based?

COLORTEC HOLDING AS has its business address in Gressvik.

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.