BIZTRAC BETA
Rental and operating of own or leased real estate

ÅNØYBUKTA AS

Org. no. 996346463 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 172,000
Incorporated 2010
Share capital NOK 136,000

Signals

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

ÅNØYBUKTA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996346463. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 136,000, divided into 34 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå kjøp og salg av fast eiendom og investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 172,000
Est. value
NOK 157,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.9%
Satisfactory
Equity as a share of total capital

Who owns ÅNØYBUKTA AS?

VIKING CLUB AS
ÅNØYBUKTA AS
NOK 0 rev. · NOK −28,000 profit

ÅNØYBUKTA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ÅNØYBUKTA AS own?

ÅNØYBUKTA AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ÅNØYBUKTA AS

Who owns ÅNØYBUKTA AS?

VIKING CLUB AS is the largest registered owner, with 100.0%.

What is the revenue of ÅNØYBUKTA AS?

ÅNØYBUKTA AS had revenue of NOK 0 in 2024.

Where is ÅNØYBUKTA AS based?

ÅNØYBUKTA AS has its business address in Flatåsen.

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.