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

BUNNPRIS SAMFUNDET AS

Org. no. 979559518 Limited company (AS) Trondheim Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 43.2m
Operating profit NOK 787,000
Equity NOK 668,000
Incorporated 1998
Employees 15
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BUNNPRIS SAMFUNDET AS is registered as a limited company in Trondheim, Trøndelag with organisation number 979559518. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1998 and has 15 registered employees. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Dagligvarehandel og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.2m in revenue and NOK 787,000 in operating profit.

Key figures · 2024

Revenue
NOK 43.2m
Operating profit
NOK 787,000
Equity
NOK 668,000
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns BUNNPRIS SAMFUNDET AS?

ADINFERNUM AS
BUNNPRIS SAMFUNDET AS
NOK 43.2m rev. · NOK 787,000 profit

BUNNPRIS SAMFUNDET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUNNPRIS SAMFUNDET AS

Who owns BUNNPRIS SAMFUNDET AS?

ADINFERNUM AS is the largest registered owner, with 100.0%.

What is the revenue of BUNNPRIS SAMFUNDET AS?

BUNNPRIS SAMFUNDET AS had revenue of NOK 43.2m in 2024.

Where is BUNNPRIS SAMFUNDET AS based?

BUNNPRIS SAMFUNDET AS has its business address in Trondheim.

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.