BIZTRAC BETA
Graphic design and visual communication activities

COOLGREY INVEST AS

Org. no. 929263421 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 31,000
Operating profit NOK −7,000
Equity NOK 15,000
Incorporated 2022
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

COOLGREY INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 929263421. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 1000 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 31,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 31,000
Operating profit
NOK −7,000
Equity
NOK 15,000
Est. value
NOK 37,000

Financial health · 2024

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

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

Who owns COOLGREY INVEST AS?

AUSRA BUCKUTÉ
COOLGREY INVEST AS
NOK 31,000 rev. · NOK −7,000 profit

COOLGREY INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does COOLGREY INVEST AS own?

COOLGREY INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about COOLGREY INVEST AS

Who owns COOLGREY INVEST AS?

AUSRA BUCKUTÉ is the largest registered owner, with 100.0%.

What is the revenue of COOLGREY INVEST AS?

COOLGREY INVEST AS had revenue of NOK 31,000 in 2024.

Where is COOLGREY INVEST AS based?

COOLGREY INVEST AS has its business address in Drammen.

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.