BIZTRAC BETA
COMPANY REGISTER PROFILE
968490036 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Operation of sports facilities

SULA RIDE OG FRITIDSENTER AS

Org. no. 968490036 Limited company (AS) Sula Incorporated 1993 Active
Ownership graph ↗
Revenue 2025 NOK 556,000
Operating profit NOK 124,000
Equity NOK 330,000
Incorporated 1993
Share capital NOK 167,000

SULA RIDE OG FRITIDSENTER AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 968490036. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 1993. Registered share capital is NOK 167,000. The company's stated purpose is: “Eige og drive eit ride- og fritidssenter- som omfattar eit fylkesanlegg i Langevåg. I dette ligg tilrettelegging for å utvikle kompetanse med til- høyrande aktivitetar for stell og bruk av hest og andre dyr som naturleg høyrer med til eit ride- og fritidssenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 556,000 in revenue and NOK 124,000 in operating profit.

Key figures · 2025

Revenue
NOK 556,000
▲ +26 %
Operating profit
NOK 124,000
▼ −33 %
Equity
NOK 330,000
▼ −0 %
Est. value
NOK 475,000

Financial health · 2025

Liquidity
2.72
Very good
Current assets ÷ current liabilities
Profitability
5.7%
Weak
Return on total assets
Solidity
14.5%
Satisfactory
Equity as a share of total capital

Who owns SULA RIDE OG FRITIDSENTER AS?

No shareholders are registered for SULA RIDE OG FRITIDSENTER AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SULA RIDE OG FRITIDSENTER AS

What is the revenue of SULA RIDE OG FRITIDSENTER AS?

SULA RIDE OG FRITIDSENTER AS had revenue of NOK 556,000 in 2025.

Where is SULA RIDE OG FRITIDSENTER AS based?

SULA RIDE OG FRITIDSENTER AS has its business address in Langevåg.

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.