biztrac. BETA
COMPANY REGISTER PROFILE
935889588 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Web search portal activities

AURALIS AS

Org. no. 935889588 Limited company (AS) Trondheim Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −12,000
Equity NOK 11,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

AURALIS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 935889588. The business is classified under web search portal activities (NACE 63.910). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av nettjenester for oppslag av offentlig kjøretøyinfo fra Statens vegvesen.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −12,000
Equity
NOK 11,000
Est. value
NOK 32,000

Financial health · 2025

Liquidity
6.79
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
85.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AURALIS AS?

AURALIS AS
NOK 16,000 rev. · NOK −12,000 profit

AURALIS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AURALIS AS

Who owns AURALIS AS?

Tobias Sjøtrø Åmot is the largest registered owner, with 50.0%.

What is the revenue of AURALIS AS?

AURALIS AS had revenue of NOK 16,000 in 2025.

Who is the general manager of AURALIS AS?

Tobias Sjøtrø Åmot is registered as general manager of AURALIS AS.

Where is AURALIS AS based?

AURALIS AS has its business address in Trondheim.

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

Report a problem

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