BIZTRAC BETA
Plumbing installation

BASBERG INVEST AS

Org. no. 923161368 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK −71,000
Incorporated 2019
Share capital NOK 150,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−71k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BASBERG INVEST AS is registered as a limited company in Tønsberg, Vestfold with organisation number 923161368. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2019. Registered share capital is NOK 150,000, divided into 1000 shares. The company's stated purpose is: “Eie, delta og investere i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK −71,000

Financial health · 2025

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

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

Who owns BASBERG INVEST AS?

PRENT-HAMER HOLDING AS
BASBERG INVEST AS
· NOK −2,000 profit

BASBERG INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BASBERG INVEST AS own?

BASBERG INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BASBERG INVEST AS

Who owns BASBERG INVEST AS?

PRENT-HAMER HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of BASBERG INVEST AS?

Christian Klemo is registered as general manager of BASBERG INVEST AS.

Where is BASBERG INVEST AS based?

BASBERG INVEST AS has its business address in Tønsberg.

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.