BIZTRAC BETA
COMPANY REGISTER PROFILE
936247962 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KAIMANA AS

Org. no. 936247962 Limited company (AS) Gjøvik Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 22,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-19.

KAIMANA AS is registered as a limited company in Gjøvik, Innlandet with organisation number 936247962. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i aksjer og andeler samt alt hva som her står i forbindelse med.”.

Key figures · 2025

Operating profit
NOK −1,000
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2025

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

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

Who owns KAIMANA AS?

KAIMANA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAIMANA AS

Who owns KAIMANA AS?

NOREASTER INVEST AS is the largest registered owner, with 50.0%.

Where is KAIMANA AS based?

KAIMANA AS has its business address in Gjøvik.

Property

Business address Bondelisvingen 20, 2816 Gjøvik
Cadastral unit 3407-57/88/0/0
Building Enebolig · 1 unit

3 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.