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

ØDEGÅRD LAVPRIS AS

Org. no. 988988170 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 80.4m
Operating profit NOK 2.0m
Equity NOK 767,000
Incorporated 2005
Share capital NOK 350,000

ØDEGÅRD LAVPRIS AS is registered as a limited company in Stavanger, Rogaland with organisation number 988988170. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2005. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Å drive handel med dagligvarer, samt hva hermed står i forbindelse, herunder å delta i andre foretagender med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 80.4m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 80.4m
Operating profit
NOK 2.0m
Equity
NOK 767,000
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns ØDEGÅRD LAVPRIS AS?

LINDA JEANETH ØDEGÅRD
ØDEGÅRD LAVPRIS AS
NOK 80.4m rev. · NOK 2.0m profit

ØDEGÅRD LAVPRIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØDEGÅRD LAVPRIS AS

Who owns ØDEGÅRD LAVPRIS AS?

LINDA JEANETH ØDEGÅRD is the largest registered owner, with 100.0%.

What is the revenue of ØDEGÅRD LAVPRIS AS?

ØDEGÅRD LAVPRIS AS had revenue of NOK 80.4m in 2024.

Who is the general manager of ØDEGÅRD LAVPRIS AS?

Linda Jeaneth Ødegård is registered as general manager of ØDEGÅRD LAVPRIS AS.

Where is ØDEGÅRD LAVPRIS AS based?

ØDEGÅRD LAVPRIS AS has its business address in Stavanger.

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.