biztrac. BETA
COMPANY REGISTER PROFILE
934394739 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

KB KB HOLDING AS

Org. no. 934394739 Limited company (AS) Stjørdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 2.9m
Incorporated 2024
Share capital NOK 40,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).
  • Nylig endring 2026-05-15 Adresseendring registrert 2026-05-15.

KB KB HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 934394739. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Investere og eie aksjer i andre selskap, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 2.9m
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
313.92
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns KB KB HOLDING AS?

KB KB HOLDING AS
NOK 0 rev. · NOK −17,000 profit

KB KB HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KB KB HOLDING AS own?

KB KB HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KB KB HOLDING AS

Who owns KB KB HOLDING AS?

Kristian Berg is the largest registered owner, with 80.0%.

What is the revenue of KB KB HOLDING AS?

KB KB HOLDING AS had revenue of NOK 0 in 2025.

Where is KB KB HOLDING AS based?

KB KB HOLDING AS has its business address in Stjørdal.

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.