BIZTRAC BETA
Operation of sports facilities

NØTTERØY GOLFBANE AS

Org. no. 981908090 Limited company (AS) Færder Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 22.4m
Operating profit NOK 853,000
Equity NOK 12.9m
Incorporated 2000
Employees 16
Share capital NOK 504,000

NØTTERØY GOLFBANE AS is registered as a limited company in Færder, Vestfold with organisation number 981908090. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2000 and has 16 registered employees. Registered share capital is NOK 504,000, divided into 1345 shares. The company's stated purpose is: “Å utvikle, finansiere, eie og drivegolfanlegg, samt annen idrettslig virksomhet som naturlig faller inn under dette. Selskapet er uten eget økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.4m in revenue and NOK 853,000 in operating profit.

Key figures · 2025

Revenue
NOK 22.4m
Operating profit
NOK 853,000
Equity
NOK 12.9m
Est. value
NOK 10.4m

Financial health · 2025

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

Who owns NØTTERØY GOLFBANE AS?

NØTTERØY GOLFKLUBB
NØTTERØY GOLFBANE AS
NOK 22.4m rev. · NOK 853,000 profit

NØTTERØY GOLFBANE AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about NØTTERØY GOLFBANE AS

Who owns NØTTERØY GOLFBANE AS?

NØTTERØY GOLFKLUBB is the largest registered owner, with 95.5%.

What is the revenue of NØTTERØY GOLFBANE AS?

NØTTERØY GOLFBANE AS had revenue of NOK 22.4m in 2025.

Who is the general manager of NØTTERØY GOLFBANE AS?

Mats Simon Augustsson is registered as general manager of NØTTERØY GOLFBANE AS.

Where is NØTTERØY GOLFBANE AS based?

NØTTERØY GOLFBANE AS has its business address in Nøtterøy.

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.