biztrac. BETA
COMPANY REGISTER PROFILE
928549151 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

CURRENT GROWTH AS

Org. no. 928549151 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −21,000
Equity NOK 8.5m
Incorporated 2022
Share capital NOK 60,000

Signals

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

CURRENT GROWTH AS is registered as a limited company in Oslo, Oslo with organisation number 928549151. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og andre selskapsandeler, eiendom og andre aktiva, samt annen virksomhet som naturlig faller inn under slik forretningsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −21,000 in operating profit.

Former names: WR START UP 446 AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −21,000
▼ −2 %
Equity
NOK 8.5m
▼ −0 %
Est. value
NOK 10.0m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns CURRENT GROWTH AS?

CURRENT GROWTH AS has 5 registered shareholders:

All shareholders and roles →

Which companies does CURRENT GROWTH AS own?

CURRENT GROWTH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CURRENT GROWTH AS

Who owns CURRENT GROWTH AS?

STEELBIRD AS is the largest registered owner, with 42.9%.

What is the revenue of CURRENT GROWTH AS?

CURRENT GROWTH AS had revenue of NOK 0 in 2025.

Where is CURRENT GROWTH AS based?

CURRENT GROWTH AS has its business address in Oslo.

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.