BIZTRAC BETA
Other education activities

TRIVSELSLEDER AS

Org. no. 995914859 Limited company (AS) Lillestrøm Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 17.6m
Operating profit NOK 5.6m
Equity NOK 2.9m
Incorporated 2010
Employees 8
Share capital NOK 80,000

TRIVSELSLEDER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 995914859. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2010 and has 8 registered employees. Registered share capital is NOK 80,000, divided into 800 shares. The company's stated purpose is: “Utviklet og driver trivselsprogrammet "Trivselsleder TL". Trivselsprogrammet er et program for mer aktivitet og økt trygghet i friminuttene i grunnskolen. I tillegg driver Trivselsleder AS med salg av leke- og aktivitetsutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.6m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 17.6m
Operating profit
NOK 5.6m
Equity
NOK 2.9m
Est. value
NOK 19.6m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.3%
Good
Equity as a share of total capital

Who owns TRIVSELSLEDER AS?

EIDE CONSULTING AS
TRIVSELSLEDER AS
NOK 17.6m rev. · NOK 5.6m profit

TRIVSELSLEDER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRIVSELSLEDER AS

Who owns TRIVSELSLEDER AS?

EIDE CONSULTING AS is the largest registered owner, with 50.0%.

What is the revenue of TRIVSELSLEDER AS?

TRIVSELSLEDER AS had revenue of NOK 17.6m in 2024.

Who is the general manager of TRIVSELSLEDER AS?

Kjartan Eide is registered as general manager of TRIVSELSLEDER AS.

Where is TRIVSELSLEDER AS based?

TRIVSELSLEDER AS has its business address in Lillestrøm.

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.