BIZTRAC BETA
Retail sale of other new goods

CHASING RAINBOWS AS

Org. no. 911683520 Limited company (AS) Kristiansand Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12,000
Operating profit NOK −29
Equity NOK 52,000
Incorporated 2013
Share capital NOK 150,000

Signals

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

CHASING RAINBOWS AS is registered as a limited company in Kristiansand, Agder with organisation number 911683520. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2013. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Salg på Internett og drift av web-portaler, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 12,000 in revenue and NOK −29 in operating profit.

Key figures · 2024

Revenue
NOK 12,000
Operating profit
NOK −29
Equity
NOK 52,000
Est. value
NOK 29,000

Financial health · 2024

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

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

Who owns CHASING RAINBOWS AS?

LUDVIG HOEL
CHASING RAINBOWS AS
NOK 12,000 rev. · NOK −29 profit

CHASING RAINBOWS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CHASING RAINBOWS AS

Who owns CHASING RAINBOWS AS?

LUDVIG HOEL is the largest registered owner, with 50.0%.

What is the revenue of CHASING RAINBOWS AS?

CHASING RAINBOWS AS had revenue of NOK 12,000 in 2024.

Who is the general manager of CHASING RAINBOWS AS?

Ludvig Hoel is registered as general manager of CHASING RAINBOWS AS.

Where is CHASING RAINBOWS AS based?

CHASING RAINBOWS 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.