BIZTRAC BETA
Business and other management consultancy activities

KJBP INVEST AS

Org. no. 921470282 Limited company (AS) Ullensaker Incorporated 2018 Active
Ownership graph ↗
Equity NOK −15,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

KJBP INVEST AS is registered as a limited company in Ullensaker, Akershus with organisation number 921470282. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tjenesteyting eller utøve annen virksomhet innenfor investerings- og forvaltningsvirksomhet, herunder deltakelse i andre selskaper, erverv av aksjer og andre selskapsandeler, erverv og drift av fast eiendom og annet realregistrerbart løsøre, samt all hertil hørende virksomhet. Investering- og kjøp av aksjer i andre selskap, samt virksomhet som naturlig hører inn under dette. Selskapet kan være eier av andre selskaper.”.

Key figures · 2025

Equity
NOK −15,000

Financial health · 2025

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

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

Who owns KJBP INVEST AS?

ANTONSEN HOLDING AS
KJBP INVEST AS

KJBP INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KJBP INVEST AS

Who owns KJBP INVEST AS?

ANTONSEN HOLDING AS is the largest registered owner, with 99.7%.

Who is the general manager of KJBP INVEST AS?

Kjersti Antonsen Jocumsen is registered as general manager of KJBP INVEST AS.

Where is KJBP INVEST AS based?

KJBP INVEST AS has its business address in Jessheim.

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.