BIZTRAC BETA
Operation of sports facilities

LYSEBOTN DISCGOLF AS

Org. no. 927932334 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 67,000
Operating profit NOK −33,000
Equity NOK −38,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

LYSEBOTN DISCGOLF AS is registered as a limited company in Stavanger, Rogaland with organisation number 927932334. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Etablering og drift av Lysebotn Discgolf, herunder også tilbyder av overnatting og servering.”. The most recent filed accounts, for the 2025 financial year, show NOK 67,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 67,000
Operating profit
NOK −33,000
Equity
NOK −38,000

Financial health · 2025

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

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

Who owns LYSEBOTN DISCGOLF AS?

TROND OLAV TANGEN
LYSEBOTN DISCGOLF AS
NOK 67,000 rev. · NOK −33,000 profit

LYSEBOTN DISCGOLF AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about LYSEBOTN DISCGOLF AS

Who owns LYSEBOTN DISCGOLF AS?

TROND OLAV TANGEN is the largest registered owner, with 91.0%.

What is the revenue of LYSEBOTN DISCGOLF AS?

LYSEBOTN DISCGOLF AS had revenue of NOK 67,000 in 2025.

Where is LYSEBOTN DISCGOLF AS based?

LYSEBOTN DISCGOLF AS has its business address in Stavanger.

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.