BIZTRAC BETA
Joinery installation

CB RESTAURERING AS

Org. no. 914957273 Limited company (AS) Grimstad Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK −627,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−627k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35k kr).

CB RESTAURERING AS is registered as a limited company in Grimstad, Agder with organisation number 914957273. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekkerarbeid og restaurering av bad og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virsomhet, og kjøp og salg av aksjer eller på anne måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”.

Key figures · 2025

Operating profit
NOK −35,000
Equity
NOK −627,000

Financial health · 2025

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

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

Who owns CB RESTAURERING AS?

CHARLES SIGVART BEISLAND
CB RESTAURERING AS
· NOK −35,000 profit

CB RESTAURERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CB RESTAURERING AS

Who owns CB RESTAURERING AS?

CHARLES SIGVART BEISLAND is the largest registered owner, with 100.0%.

Who is the general manager of CB RESTAURERING AS?

Charles Sigvart Beisland is registered as general manager of CB RESTAURERING AS.

Where is CB RESTAURERING AS based?

CB RESTAURERING AS has its business address in Grimstad.

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.