BIZTRAC BETA
COMPANY REGISTER PROFILE
936435696 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

BKING HOLDING AS

Org. no. 936435696 Limited company (AS) Larvik Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −2
Equity NOK 33,000
Incorporated 2025
Share capital NOK 80,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2 kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-10-10.
  • Nylig endring 2026-04-14 Adresseendring registrert 2026-04-14.

BKING HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 936435696. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 80,000, divided into 40000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −2
Equity
NOK 33,000
Est. value
NOK 39,000

Financial health · 2025

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

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

Who owns BKING HOLDING AS?

BRADLEY KING
BKING HOLDING AS
· NOK −2 profit

BKING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BKING HOLDING AS own?

BKING HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BKING HOLDING AS

Who owns BKING HOLDING AS?

BRADLEY KING is the largest registered owner, with 100.0%.

Where is BKING HOLDING AS based?

BKING HOLDING AS has its business address in Tjodalyng.

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.