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

SØRBØVÅG BUTIKKDRIFT AS

Org. no. 918120513 Limited company (AS) Hyllestad Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 403,000
Equity NOK 2.1m
Incorporated 2016
Share capital NOK 30,000

Signals

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

SØRBØVÅG BUTIKKDRIFT AS is registered as a limited company in Hyllestad, Vestland with organisation number 918120513. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Dagligvarehandel samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 403,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 403,000
Equity
NOK 2.1m
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns SØRBØVÅG BUTIKKDRIFT AS?

SØRBØVÅG SENTER AS
SØRBØVÅG BUTIKKDRIFT AS
NOK 9.9m rev. · NOK 403,000 profit

SØRBØVÅG BUTIKKDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRBØVÅG BUTIKKDRIFT AS

Who owns SØRBØVÅG BUTIKKDRIFT AS?

SØRBØVÅG SENTER AS is the largest registered owner, with 100.0%.

What is the revenue of SØRBØVÅG BUTIKKDRIFT AS?

SØRBØVÅG BUTIKKDRIFT AS had revenue of NOK 9.9m in 2024.

Where is SØRBØVÅG BUTIKKDRIFT AS based?

SØRBØVÅG BUTIKKDRIFT AS has its business address in Sørbøvåg.

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.