BIZTRAC BETA
COMPANY REGISTER PROFILE
934388550 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 02.09.2026
ÅÅÅ AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Uoppgitt

ÅÅÅ AS

Org. no. 934388550 Limited company (AS) Tysvær Incorporated 2024 In liquidation
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 16,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

ÅÅÅ AS is registered as a limited company in Tysvær, Rogaland with organisation number 934388550. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i aksjer.”.

Key figures · 2025

Operating profit
NOK −14,000
Equity
NOK 16,000

Financial health · 2025

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

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

Who owns ÅÅÅ AS?

ÅÅÅ AS
· NOK −14,000 profit

ÅÅÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅÅÅ AS

Who owns ÅÅÅ AS?

Tobias Østhus is the largest registered owner, with 100.0%.

Where is ÅÅÅ AS based?

ÅÅÅ AS has its business address in Førresfjorden.

Property

Business address c/o Heidi Gerhard Vestli 39, 5563 Førresfjorden
Cadastral unit 1146-79/193/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.