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

KIMBERLITE INVEST NOFENCE AS

Org. no. 832587052 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −12,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

KIMBERLITE INVEST NOFENCE AS is registered as a limited company in Oslo, Oslo with organisation number 832587052. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 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 −12,000
▲ +34 %

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

Who owns KIMBERLITE INVEST NOFENCE AS?

KIMBERLITE INVEST NOFENCE AS has 14 registered shareholders:

All shareholders and roles →

Which companies does KIMBERLITE INVEST NOFENCE AS own?

KIMBERLITE INVEST NOFENCE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KIMBERLITE INVEST NOFENCE AS

Who owns KIMBERLITE INVEST NOFENCE AS?

Bo Joachim Kähler is the largest registered owner, with 22.6%.

Who is the general manager of KIMBERLITE INVEST NOFENCE AS?

Guttorm Hoff is registered as general manager of KIMBERLITE INVEST NOFENCE AS.

Where is KIMBERLITE INVEST NOFENCE AS based?

KIMBERLITE INVEST NOFENCE AS has its business address in Oslo.

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.