BIZTRAC BETA
COMPANY REGISTER PROFILE
830219692 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

KJØPMANN HORN AS

Org. no. 830219692 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 25.5m
Operating profit NOK 591,000
Equity NOK 2.0m
Incorporated 2022
Employees 12
Share capital NOK 350,000

KJØPMANN HORN AS is registered as a limited company in Øygarden, Vestland with organisation number 830219692. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2022 and has 12 registered employees. Registered share capital is NOK 350,000, divided into 1000 shares. The company's stated purpose is: “Dagligvarehandel.”. The most recent filed accounts, for the 2025 financial year, show NOK 25.5m in revenue and NOK 591,000 in operating profit.

Key figures · 2025

Revenue
NOK 25.5m
▲ +12 %
Operating profit
NOK 591,000
▼ −27 %
Equity
NOK 2.0m
▲ +19 %
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns KJØPMANN HORN AS?

KJØPMANN HORN AS
NOK 25.5m rev. · NOK 591,000 profit

KJØPMANN HORN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJØPMANN HORN AS

Who owns KJØPMANN HORN AS?

KJØPMANN HORN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KJØPMANN HORN AS?

KJØPMANN HORN AS had revenue of NOK 25.5m in 2025.

Who is the general manager of KJØPMANN HORN AS?

Kim-Rune Horn is registered as general manager of KJØPMANN HORN AS.

Where is KJØPMANN HORN AS based?

KJØPMANN HORN AS has its business address in Brattholmen.

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.