BIZTRAC BETA
Operation of sports facilities

NORSJØ GOLFPARK AS

Org. no. 981341384 Limited company (AS) Nome Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 446,000
Equity NOK 6.3m
Incorporated 1999
Employees 6
Share capital NOK 2.2m

NORSJØ GOLFPARK AS is registered as a limited company in Nome, Telemark with organisation number 981341384. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 1999 and has 6 registered employees. Registered share capital is NOK 2.2m, divided into 1000 shares. The company's stated purpose is: “Forvalte Norsjø Golfparks golfbane beliggende i Nome kommune ved utleie til Norsjø Golfklubb, samt annen virksomhet som naturlig hører inn under golfsporten. Selskapet er uten eget økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 446,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
Operating profit
NOK 446,000
Equity
NOK 6.3m
Est. value
NOK 5.8m

Financial health · 2025

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

Who owns NORSJØ GOLFPARK AS?

NORSJØ GOLFKLUBB
NORSJØ GOLFPARK AS
NOK 13.0m rev. · NOK 446,000 profit

NORSJØ GOLFPARK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORSJØ GOLFPARK AS

Who owns NORSJØ GOLFPARK AS?

NORSJØ GOLFKLUBB is the largest registered owner, with 100.0%.

What is the revenue of NORSJØ GOLFPARK AS?

NORSJØ GOLFPARK AS had revenue of NOK 13.0m in 2025.

Who is the general manager of NORSJØ GOLFPARK AS?

Ragnar Kisfoss is registered as general manager of NORSJØ GOLFPARK AS.

Where is NORSJØ GOLFPARK AS based?

NORSJØ GOLFPARK AS has its business address in Ulefoss.

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.