BIZTRAC BETA
Activities of excursion and event organisers

ESTANGARD AS

Org. no. 929555260 Limited company (AS) Ullensvang Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 191,000
Operating profit NOK 18,000
Equity NOK 37,000
Incorporated 2022
Share capital NOK 45,000

Signals

1 flags
  • Nylig endring 2026-04-20 Adresseendring registrert 2026-04-20.

ESTANGARD AS is registered as a limited company in Ullensvang, Vestland with organisation number 929555260. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2022. Registered share capital is NOK 45,000, divided into 45 shares. The company's stated purpose is: “Ekstraordinære opplevelser, events og overnatting. Guidetjenester, aktiviteter, turer og kurs. Utleie av overnatting og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 191,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 191,000
Operating profit
NOK 18,000
Equity
NOK 37,000
Est. value
NOK 101,000

Financial health · 2025

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

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

Who owns ESTANGARD AS?

ANGEL DIMITROV KOLEV
ESTANGARD AS
NOK 191,000 rev. · NOK 18,000 profit

ESTANGARD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ESTANGARD AS

Who owns ESTANGARD AS?

ANGEL DIMITROV KOLEV is the largest registered owner, with 33.3%.

What is the revenue of ESTANGARD AS?

ESTANGARD AS had revenue of NOK 191,000 in 2025.

Who is the general manager of ESTANGARD AS?

Richard Mauseth is registered as general manager of ESTANGARD AS.

Where is ESTANGARD AS based?

ESTANGARD AS has its business address in Hovland.

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.