biztrac. BETA
COMPANY REGISTER PROFILE
915994245 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other real estate activities on a fee or contract basis

TRIVSELSSKOGEN SA

Org. no. 915994245 Co-operation (SA) Gloppen Incorporated 2015 Active
Revenue 2025 NOK 541,000
Operating profit NOK 422,000
Equity NOK 788,000
Incorporated 2015

TRIVSELSSKOGEN SA is registered as a co-operation in Gloppen, Vestland with organisation number 915994245. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2015. The company's stated purpose is: “Tilrettelegge, utvikle og vedlikehalde sentrumsnært turområde med tanke på betre folkehelse. Dette skal m.a. gjennomførast ved opparbeiding av turløyper til Utsikten og Fossen med etablering av plattformer og trapper, klatre og buldrevegg, naturmøteplassar og stinettverk med kvile- og møteplassar samt rydding, skilting og lyssetting. Deler av prosjektet skal tilpassast rørslehemma.”. The most recent filed accounts, for the 2025 financial year, show NOK 541,000 in revenue and NOK 422,000 in operating profit.

Key figures · 2025

Revenue
NOK 541,000
▲ +97 %
Operating profit
NOK 422,000
▲ +373 %
Equity
NOK 788,000
▲ +115 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
34.04
Very good
Current assets ÷ current liabilities
Profitability
71.3%
Very good
Return on total assets
Solidity
97.1%
Very good
Equity as a share of total capital

Who owns TRIVSELSSKOGEN SA?

No shareholders are registered for TRIVSELSSKOGEN SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TRIVSELSSKOGEN SA

What is the revenue of TRIVSELSSKOGEN SA?

TRIVSELSSKOGEN SA had revenue of NOK 541,000 in 2025.

Where is TRIVSELSSKOGEN SA based?

TRIVSELSSKOGEN SA has its business address in Sandane.

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

Report a problem

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