BIZTRAC BETA
Uoppgitt

KINNABAKKEN AS

Org. no. 927727277 Limited company (AS) Gjemnes Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 6.5m
Incorporated 2021
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

KINNABAKKEN AS is registered as a limited company in Gjemnes, Møre og Romsdal with organisation number 927727277. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 35,000, divided into 70 shares. The company's stated purpose is: “Investering i andre selskap, aksjer, verdipapirer og eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 6.5m
Est. value
NOK 9.1m

Financial health · 2024

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

Who owns KINNABAKKEN AS?

TROND HOEM
KINNABAKKEN AS
NOK 0 rev. · NOK −16,000 profit

KINNABAKKEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KINNABAKKEN AS own?

KINNABAKKEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KINNABAKKEN AS

Who owns KINNABAKKEN AS?

TROND HOEM is the largest registered owner, with 100.0%.

What is the revenue of KINNABAKKEN AS?

KINNABAKKEN AS had revenue of NOK 0 in 2024.

Who is the general manager of KINNABAKKEN AS?

Trond Hoem is registered as general manager of KINNABAKKEN AS.

Where is KINNABAKKEN AS based?

KINNABAKKEN AS has its business address in Flemma.

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.