BIZTRAC BETA
Business and other management consultancy activities

KBI FINANCIAL MANAGEMENT AS

Org. no. 915104495 Limited company (AS) Jevnaker Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 267,000
Incorporated 2015
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

KBI FINANCIAL MANAGEMENT AS is registered as a limited company in Jevnaker, Akershus with organisation number 915104495. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 300,000, divided into 30000 shares. The company's stated purpose is: “Å tilby konsulenttjenester innen bedrifts- og økonomiledelse, i tillegg til andre konsulent- og rådgivningstjenester, deltakelse i andre virksomheter, samt alt som kommer inn under dette.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 267,000
Est. value
NOK 434,000

Financial health · 2025

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

Who owns KBI FINANCIAL MANAGEMENT AS?

PLAYGROUND CAPITAL AS
KBI FINANCIAL MANAGEMENT AS
· NOK −4,000 profit

KBI FINANCIAL MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KBI FINANCIAL MANAGEMENT AS er morselskap for 1 datterselskap:

Frequently asked questions about KBI FINANCIAL MANAGEMENT AS

Who owns KBI FINANCIAL MANAGEMENT AS?

PLAYGROUND CAPITAL AS is the largest registered owner, with 100.0%.

Who is the general manager of KBI FINANCIAL MANAGEMENT AS?

Kjartan Bø is registered as general manager of KBI FINANCIAL MANAGEMENT AS.

Where is KBI FINANCIAL MANAGEMENT AS based?

KBI FINANCIAL MANAGEMENT AS has its business address in Jevnaker.

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.