BIZTRAC BETA
Office administrative and support activities

AWAZE AS

Org. no. 932629739 Limited company (AS) Ringsaker Incorporated 1982 Active
Ownership graph ↗
Revenue 2024 NOK 16.4m
Operating profit NOK 1.5m
Equity NOK 2.9m
Incorporated 1982
Employees 9
Share capital NOK 100,000

Signals

1 flags
  • Nylig endring 2026-03-02 Adresseendring registrert 2026-03-02.

AWAZE AS is registered as a limited company in Ringsaker, Innlandet with organisation number 932629739. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 1982 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Å utføre administrative og forretningsmessige støttetjenester, samt markedsføring på vegne av AWAZE org.nr. 993 559 474.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.4m in revenue and NOK 1.5m in operating profit.

Key figures · 2024

Revenue
NOK 16.4m
Operating profit
NOK 1.5m
Equity
NOK 2.9m
Est. value
NOK 8.0m

Financial health · 2024

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

Who owns AWAZE AS?

AWAZE AS
AWAZE AS
NOK 16.4m rev. · NOK 1.5m profit

AWAZE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AWAZE AS own?

AWAZE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AWAZE AS

Who owns AWAZE AS?

AWAZE AS is the largest registered owner, with 100.0%.

What is the revenue of AWAZE AS?

AWAZE AS had revenue of NOK 16.4m in 2024.

Who is the general manager of AWAZE AS?

Martin Rovsing is registered as general manager of AWAZE AS.

Where is AWAZE AS based?

AWAZE AS has its business address in Mesnali.

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.