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

BUNNPRIS STORTUA AS

Org. no. 965614001 Limited company (AS) Kristiansund Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 59.0m
Operating profit NOK 2.2m
Equity NOK 2.3m
Incorporated 1992
Employees 19
Share capital NOK 200,000

BUNNPRIS STORTUA AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 965614001. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1992 and has 19 registered employees. Registered share capital is NOK 200,000, divided into 20000 shares. The company's stated purpose is: “Handel med dagligvarer samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 59.0m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 59.0m
Operating profit
NOK 2.2m
Equity
NOK 2.3m
Est. value
NOK 9.7m

Financial health · 2024

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

Who owns BUNNPRIS STORTUA AS?

No shareholders are registered for BUNNPRIS STORTUA AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Group structure

BUNNPRIS STORTUA AS er morselskap for 24 datterselskaper:

Frequently asked questions about BUNNPRIS STORTUA AS

What is the revenue of BUNNPRIS STORTUA AS?

BUNNPRIS STORTUA AS had revenue of NOK 59.0m in 2024.

Who is the general manager of BUNNPRIS STORTUA AS?

Marit Indergård Kopstad is registered as general manager of BUNNPRIS STORTUA AS.

Where is BUNNPRIS STORTUA AS based?

BUNNPRIS STORTUA AS has its business address in Kristiansund N.

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.