BIZTRAC BETA
COMPANY REGISTER PROFILE
990754810 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

BELLINGEN AS

Org. no. 990754810 Limited company (AS) Ørsta Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 12.9m
Operating profit NOK 1.1m
Equity NOK 10.1m
Incorporated 2006
Employees 12
Share capital NOK 100,000

BELLINGEN AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 990754810. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2006 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med vidt varespekter og skaffe seg eierinteresse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.9m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 12.9m
▲ +3 %
Operating profit
NOK 1.1m
▼ −4 %
Equity
NOK 10.1m
▲ +11 %
Est. value
NOK 9.4m

Financial health · 2025

Liquidity
9.41
Very good
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
90.2%
Very good
Equity as a share of total capital

Who owns BELLINGEN AS?

BELLINGEN AS
NOK 12.9m rev. · NOK 1.1m profit

BELLINGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BELLINGEN AS

Who owns BELLINGEN AS?

JON ARNE ÅRSETH is the largest registered owner, with 100.0%.

What is the revenue of BELLINGEN AS?

BELLINGEN AS had revenue of NOK 12.9m in 2025.

Who is the general manager of BELLINGEN AS?

Jon Arne Årseth is registered as general manager of BELLINGEN AS.

Where is BELLINGEN AS based?

BELLINGEN AS has its business address in Sæbø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.