BIZTRAC BETA
Activities of adventure companies

FOLGEFONNI BREFØRARLAG AS

Org. no. 988418536 Limited company (AS) Ullensvang Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 747,000
Equity NOK 2.3m
Incorporated 2005
Share capital NOK 100,000

FOLGEFONNI BREFØRARLAG AS is registered as a limited company in Ullensvang, Vestland with organisation number 988418536. The business is classified under activities of adventure companies (NACE 93.291). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Breføring, klatreføring, kajakkføring og fjellføring på Folgefonnhalvøya med hovedvekt på aktivitetene knyttet til Folgefonna.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 747,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 747,000
Equity
NOK 2.3m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns FOLGEFONNI BREFØRARLAG AS?

ÅSMUND BAKKE
FOLGEFONNI BREFØRARLAG AS
NOK 7.4m rev. · NOK 747,000 profit

FOLGEFONNI BREFØRARLAG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FOLGEFONNI BREFØRARLAG AS

Who owns FOLGEFONNI BREFØRARLAG AS?

ÅSMUND BAKKE is the largest registered owner, with 51.0%.

What is the revenue of FOLGEFONNI BREFØRARLAG AS?

FOLGEFONNI BREFØRARLAG AS had revenue of NOK 7.4m in 2024.

Who is the general manager of FOLGEFONNI BREFØRARLAG AS?

Åsmund Bakke is registered as general manager of FOLGEFONNI BREFØRARLAG AS.

Where is FOLGEFONNI BREFØRARLAG AS based?

FOLGEFONNI BREFØRARLAG AS has its business address in Jondal.

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.