BIZTRAC BETA
Other recreational activities

FURUSJØEN RUNDT AS

Org. no. 913776909 Limited company (AS) Nord-Fron Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 2,000
Equity NOK 37,000
Incorporated 2014
Share capital NOK 30,000

FURUSJØEN RUNDT AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 913776909. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Styrke interessen for aktivt friluftsliv og idrett gjennom å arrangere Furusjøen Rundt-trippelen samt etablere og delta i andre tiltak som bidrar til og styrker aktiviteten i Kvam idrettslag. Selskapet kan kjøpe og eie andeler i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 2,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 2,000
Equity
NOK 37,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns FURUSJØEN RUNDT AS?

No shareholders are registered for FURUSJØEN RUNDT AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about FURUSJØEN RUNDT AS

What is the revenue of FURUSJØEN RUNDT AS?

FURUSJØEN RUNDT AS had revenue of NOK 1.0m in 2025.

Who is the general manager of FURUSJØEN RUNDT AS?

Ole Petter Brendstuen is registered as general manager of FURUSJØEN RUNDT AS.

Where is FURUSJØEN RUNDT AS based?

FURUSJØEN RUNDT AS has its business address in Kvam.

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.