biztrac. BETA
COMPANY REGISTER PROFILE
831636262 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

K. BERG HOLDING AS

Org. no. 831636262 Limited company (AS) Vestvågøy Incorporated 2023 Active
Operating profit NOK −24,000
Equity NOK −12,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−12k kr).

K. BERG HOLDING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 831636262. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Direkte og indirekte investering i andre selskaper og virksomheter.”.

Key figures · 2025

Operating profit
NOK −24,000
▼ −47 %
Equity
NOK −12,000
▼ −188 %

Financial health · 2025

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

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

Who owns K. BERG HOLDING AS?

K. BERG HOLDING AS
· NOK −24,000 profit

K. BERG HOLDING AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Which companies does K. BERG HOLDING AS own?

K. BERG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about K. BERG HOLDING AS

Who owns K. BERG HOLDING AS?

Kristoffer Berg is the largest registered owner, with 100.0%.

Who is the general manager of K. BERG HOLDING AS?

Kristoffer Berg is registered as general manager of K. BERG HOLDING AS.

Where is K. BERG HOLDING AS based?

K. BERG HOLDING AS has its business address in Stamsund.

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.