BIZTRAC BETA
Other non-specialised retail sale

OS LAVPRIS AS

Org. no. 979779992 Limited company (AS) Bjørnafjorden Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 48.6m
Operating profit NOK 204,000
Equity NOK 673,000
Incorporated 1998
Employees 19
Share capital NOK 300,000

Signals

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

OS LAVPRIS AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 979779992. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 1998 and has 19 registered employees. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Handel, samt hva dermed står i forbindelser, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 48.6m in revenue and NOK 204,000 in operating profit.

Key figures · 2025

Revenue
NOK 48.6m
Operating profit
NOK 204,000
Equity
NOK 673,000
Est. value
NOK 984,000

Financial health · 2024

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.8%
Weak
Equity as a share of total capital

Who owns OS LAVPRIS AS?

MB BUTIKKDRIFT AS
OS LAVPRIS AS
NOK 48.6m rev. · NOK 204,000 profit

OS LAVPRIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OS LAVPRIS AS

Who owns OS LAVPRIS AS?

MB BUTIKKDRIFT AS is the largest registered owner, with 100.0%.

What is the revenue of OS LAVPRIS AS?

OS LAVPRIS AS had revenue of NOK 48.6m in 2025.

Who is the general manager of OS LAVPRIS AS?

May-Britt Nymark Skåla is registered as general manager of OS LAVPRIS AS.

Where is OS LAVPRIS AS based?

OS LAVPRIS AS has its business address in Os.

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.