BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

KIRKENG BUTIKKDRIFT AS

Org. no. 927289555 Limited company (AS) Indre Østfold Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 82.0m
Operating profit NOK 951,000
Equity NOK 3.2m
Incorporated 2021
Employees 14
Share capital NOK 500,000

KIRKENG BUTIKKDRIFT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 927289555. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2021 and has 14 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 82.0m in revenue and NOK 951,000 in operating profit.

Key figures · 2025

Revenue
NOK 82.0m
Operating profit
NOK 951,000
Equity
NOK 3.2m
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.4%
Good
Equity as a share of total capital

Who owns KIRKENG BUTIKKDRIFT AS?

GARD-EVEN KIRKENG
KIRKENG BUTIKKDRIFT AS
NOK 82.0m rev. · NOK 951,000 profit

KIRKENG BUTIKKDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KIRKENG BUTIKKDRIFT AS

Who owns KIRKENG BUTIKKDRIFT AS?

GARD-EVEN KIRKENG is the largest registered owner, with 100.0%.

What is the revenue of KIRKENG BUTIKKDRIFT AS?

KIRKENG BUTIKKDRIFT AS had revenue of NOK 82.0m in 2025.

Where is KIRKENG BUTIKKDRIFT AS based?

KIRKENG BUTIKKDRIFT AS has its business address in Spydeberg.

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.