BIZTRAC BETA
Rental and leasing of recreational and sports goods

SIMULATORGOLF AS

Org. no. 926134825 Limited company (AS) Kviteseid Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 306,000
Equity NOK −85,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−85k kr).

SIMULATORGOLF AS is registered as a limited company in Kviteseid, Telemark with organisation number 926134825. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Opplevelsesrelaterte varer og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 306,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 306,000
Equity
NOK −85,000
Est. value
NOK 1.5m

Financial health · 2024

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

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

Who owns SIMULATORGOLF AS?

LIMITLESS HOLDING AS
SIMULATORGOLF AS
NOK 1.9m rev. · NOK 306,000 profit

SIMULATORGOLF AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SIMULATORGOLF AS own?

SIMULATORGOLF AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SIMULATORGOLF AS

Who owns SIMULATORGOLF AS?

LIMITLESS HOLDING AS is the largest registered owner, with 31.7%.

What is the revenue of SIMULATORGOLF AS?

SIMULATORGOLF AS had revenue of NOK 1.9m in 2024.

Where is SIMULATORGOLF AS based?

SIMULATORGOLF AS has its business address in Kviteseid.

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.