BIZTRAC BETA
Activities of tour guides

KVAM GUIDING OG SERVICE AS

Org. no. 926442295 Limited company (AS) Luster Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 688,000
Operating profit NOK 294,000
Equity NOK 107,000
Incorporated 2021
Share capital NOK 30,000

KVAM GUIDING OG SERVICE AS is registered as a limited company in Luster, Vestland with organisation number 926442295. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Guiding av turister, salg fiskeutstyr utleie og logistikk og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 688,000 in revenue and NOK 294,000 in operating profit.

Key figures · 2024

Revenue
NOK 688,000
Operating profit
NOK 294,000
Equity
NOK 107,000
Est. value
NOK 920,000

Financial health · 2024

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

Who owns KVAM GUIDING OG SERVICE AS?

RINE MERETE KVAM
KVAM GUIDING OG SERVICE AS
NOK 688,000 rev. · NOK 294,000 profit

KVAM GUIDING OG SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVAM GUIDING OG SERVICE AS

Who owns KVAM GUIDING OG SERVICE AS?

RINE MERETE KVAM is the largest registered owner, with 50.0%.

What is the revenue of KVAM GUIDING OG SERVICE AS?

KVAM GUIDING OG SERVICE AS had revenue of NOK 688,000 in 2024.

Who is the general manager of KVAM GUIDING OG SERVICE AS?

Adrianne Kvam is registered as general manager of KVAM GUIDING OG SERVICE AS.

Where is KVAM GUIDING OG SERVICE AS based?

KVAM GUIDING OG SERVICE AS has its business address in Hafslo.

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.