BIZTRAC BETA
Beverage serving activities

KVAMSKOGEN AFTERSKI AS

Org. no. 930850381 Limited company (AS) Kvam Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 506,000
Operating profit NOK 101,000
Equity NOK 340,000
Incorporated 2023
Share capital NOK 100,000

KVAMSKOGEN AFTERSKI AS is registered as a limited company in Kvam, Vestland with organisation number 930850381. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av Kvamskogen Afterski med virksomhet innen bar, drift av pub, drift av nattklubb og det som herunder faller naturlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 506,000 in revenue and NOK 101,000 in operating profit.

Key figures · 2025

Revenue
NOK 506,000
Operating profit
NOK 101,000
Equity
NOK 340,000
Est. value
NOK 553,000

Financial health · 2025

Liquidity
12.94
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.3%
Very good
Equity as a share of total capital

Who owns KVAMSKOGEN AFTERSKI AS?

AS KVAM FJELLHEISAR
KVAMSKOGEN AFTERSKI AS
NOK 506,000 rev. · NOK 101,000 profit

KVAMSKOGEN AFTERSKI AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVAMSKOGEN AFTERSKI AS

Who owns KVAMSKOGEN AFTERSKI AS?

AS KVAM FJELLHEISAR is the largest registered owner, with 50.0%.

What is the revenue of KVAMSKOGEN AFTERSKI AS?

KVAMSKOGEN AFTERSKI AS had revenue of NOK 506,000 in 2025.

Who is the general manager of KVAMSKOGEN AFTERSKI AS?

Steffen Vike Holm is registered as general manager of KVAMSKOGEN AFTERSKI AS.

Where is KVAMSKOGEN AFTERSKI AS based?

KVAMSKOGEN AFTERSKI AS has its business address in Norheimsund.

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.