BIZTRAC BETA
Other personal service activities n.e.c.

ÅLESUND HUNDESENTER AS

Org. no. 933121291 Limited company (AS) Ålesund Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 642,000
Operating profit NOK −43,000
Equity NOK 28,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

ÅLESUND HUNDESENTER AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 933121291. The business is classified under other personal service activities n.e.c. (NACE 96.990). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby innendørs hundetrening, utleie av hall til trening, organiserte hundetreninger og hundekurs.”. The most recent filed accounts, for the 2025 financial year, show NOK 642,000 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 642,000
Operating profit
NOK −43,000
Equity
NOK 28,000
Est. value
NOK 462,000

Financial health · 2025

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

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

Who owns ÅLESUND HUNDESENTER AS?

INGER BEATE VONGRAVEN DYRSTAD
ÅLESUND HUNDESENTER AS
NOK 642,000 rev. · NOK −43,000 profit

ÅLESUND HUNDESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÅLESUND HUNDESENTER AS

Who owns ÅLESUND HUNDESENTER AS?

INGER BEATE VONGRAVEN DYRSTAD is the largest registered owner, with 33.3%.

What is the revenue of ÅLESUND HUNDESENTER AS?

ÅLESUND HUNDESENTER AS had revenue of NOK 642,000 in 2025.

Where is ÅLESUND HUNDESENTER AS based?

ÅLESUND HUNDESENTER AS has its business address in Ålesund.

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.