BIZTRAC BETA
Activities of agents involved in the wholesale of machinery, industrial equipment, ships and aircraft

KIM-EN AS

Org. no. 925311928 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −73,000
Equity NOK 1.1m
Incorporated 2020
Share capital NOK 30,000

Signals

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

KIM-EN AS is registered as a limited company in Bergen, Vestland with organisation number 925311928. The business is classified under activities of agents involved in the wholesale of machinery, industrial equipment, ships and aircraft (NACE 46.140). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, formidling og vedlikehold av båter, utleie av personell og konsulenttjenester og herved hva som står i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −73,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −73,000
Equity
NOK 1.1m
Est. value
NOK 1.0m

Financial health · 2024

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

Who owns KIM-EN AS?

KIM OVE KÅRDAL
KIM-EN AS
NOK 1.7m rev. · NOK −73,000 profit

KIM-EN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIM-EN AS

Who owns KIM-EN AS?

KIM OVE KÅRDAL is the largest registered owner, with 100.0%.

What is the revenue of KIM-EN AS?

KIM-EN AS had revenue of NOK 1.7m in 2024.

Who is the general manager of KIM-EN AS?

Kim Ove Kårdal is registered as general manager of KIM-EN AS.

Where is KIM-EN AS based?

KIM-EN AS has its business address in Mathopen.

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.