BIZTRAC BETA
COMPANY REGISTER PROFILE
884904102 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Activities of sports clubs

SMØLA GOLF AS

Org. no. 884904102 Limited company (AS) Smøla Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 47,000
Operating profit NOK −5,000
Equity NOK −86,000
Incorporated 2002
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−86k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

SMØLA GOLF AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 884904102. The business is classified under activities of sports clubs (NACE 93.120). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift og vedlikehold av golfanlegg, engasjere seg i lignende virksomheter, og hva som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 47,000 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 47,000
▼ −22 %
Operating profit
NOK −5,000
▼ −288 %
Equity
NOK −86,000
▼ −4 %

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-81.7%
Weak
Equity as a share of total capital

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

Who owns SMØLA GOLF AS?

SMØLA GOLF AS
NOK 47,000 rev. · NOK −5,000 profit

SMØLA GOLF AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMØLA GOLF AS

Who owns SMØLA GOLF AS?

NILS BAADNES is the largest registered owner, with 100.0%.

What is the revenue of SMØLA GOLF AS?

SMØLA GOLF AS had revenue of NOK 47,000 in 2025.

Where is SMØLA GOLF AS based?

SMØLA GOLF AS has its business address in Smøla.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.