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

NONSMAT AS

Org. no. 887010072 Limited company (AS) Aure Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 22.0m
Operating profit NOK −65,000
Equity NOK 1.2m
Incorporated 2004
Employees 15
Share capital NOK 354,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−65k kr).

NONSMAT AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 887010072. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2004 and has 15 registered employees. Registered share capital is NOK 354,000, divided into 350000 shares. The company's stated purpose is: “Dagligvareforretning samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.0m in revenue and NOK −65,000 in operating profit.

Key figures · 2024

Revenue
NOK 22.0m
Operating profit
NOK −65,000
Equity
NOK 1.2m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns NONSMAT AS?

ANNE LISE VAAG BERGDAL
NONSMAT AS
NOK 22.0m rev. · NOK −65,000 profit

NONSMAT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NONSMAT AS

Who owns NONSMAT AS?

ANNE LISE VAAG BERGDAL is the largest registered owner, with 100.0%.

What is the revenue of NONSMAT AS?

NONSMAT AS had revenue of NOK 22.0m in 2024.

Who is the general manager of NONSMAT AS?

Daniel Vaag Bergdal is registered as general manager of NONSMAT AS.

Where is NONSMAT AS based?

NONSMAT AS has its business address in Aure.

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.