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

AUDUN ØWRE AS

Org. no. 930661600 Limited company (AS) Sør-Varanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 127.3m
Operating profit NOK 1.2m
Equity NOK 2.5m
Incorporated 2023
Employees 40
Share capital NOK 500,000

AUDUN ØWRE AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 930661600. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2023 and has 40 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 127.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 127.3m
Operating profit
NOK 1.2m
Equity
NOK 2.5m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns AUDUN ØWRE AS?

AUDUN ØWRE
AUDUN ØWRE AS
NOK 127.3m rev. · NOK 1.2m profit

AUDUN ØWRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AUDUN ØWRE AS

Who owns AUDUN ØWRE AS?

AUDUN ØWRE is the largest registered owner, with 100.0%.

What is the revenue of AUDUN ØWRE AS?

AUDUN ØWRE AS had revenue of NOK 127.3m in 2025.

Who is the general manager of AUDUN ØWRE AS?

Audun Øwre is registered as general manager of AUDUN ØWRE AS.

Where is AUDUN ØWRE AS based?

AUDUN ØWRE AS has its business address in Hesseng.

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.