biztrac. BETA
COMPANY REGISTER PROFILE
927608162 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
In liquidation UPDATED 03.10.2026
⚠CHARGING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other technical consultancy

CHARGING AS

Org. no. 927608162 Limited company (AS) Stavanger Incorporated 2021 In liquidation
Ownership graph ↗
Operating profit NOK −2.2m
Equity NOK 688,000
Incorporated 2021
Share capital NOK 725,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,2 mill kr).

CHARGING AS is registered as a limited company in Stavanger, Rogaland with organisation number 927608162. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 725,000, divided into 116046102 shares. The company's stated purpose is: “Å investere i, eie, utvikle og selge selskaper og alt som står i forbindelse med dette.”.

Former names: WHITEROCK INVEST AS

Key figures · 2025

Operating profit
NOK −2.2m
▼ −94 %
Equity
NOK 688,000
▼ −100 %

Financial health · 2025

Liquidity
0.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.3%
Not satisfactory
Return on total assets
Solidity
0.5%
Not satisfactory
Equity as a share of total capital

Who owns CHARGING AS?

CHARGING AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does CHARGING AS own?

CHARGING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about CHARGING AS

Who owns CHARGING AS?

MOMENTUM II AS is the largest registered owner, with 6.2%.

Who is the general manager of CHARGING AS?

Fredrik Erland Lima is registered as general manager of CHARGING AS.

Where is CHARGING AS based?

CHARGING AS has its business address in Stavanger.

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.