BIZTRAC BETA
Business and other management consultancy activities

SENTER FOR LIVSGLEDE AS

Org. no. 924681144 Limited company (AS) Nord-Odal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 53,000
Operating profit NOK 717
Equity NOK −56,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

SENTER FOR LIVSGLEDE AS is registered as a limited company in Nord-Odal, Innlandet with organisation number 924681144. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av konsulenttjenester innen personlig utvikling, bedriftsutvikling og forvaltning av human kapital.”. The most recent filed accounts, for the 2025 financial year, show NOK 53,000 in revenue and NOK 717 in operating profit.

Key figures · 2025

Revenue
NOK 53,000
Operating profit
NOK 717
Equity
NOK −56,000
Est. value
NOK 7,000

Financial health · 2025

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

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

Who owns SENTER FOR LIVSGLEDE AS?

ROAR DONS
SENTER FOR LIVSGLEDE AS
NOK 53,000 rev. · NOK 717 profit

SENTER FOR LIVSGLEDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SENTER FOR LIVSGLEDE AS

Who owns SENTER FOR LIVSGLEDE AS?

ROAR DONS is the largest registered owner, with 100.0%.

What is the revenue of SENTER FOR LIVSGLEDE AS?

SENTER FOR LIVSGLEDE AS had revenue of NOK 53,000 in 2025.

Where is SENTER FOR LIVSGLEDE AS based?

SENTER FOR LIVSGLEDE AS has its business address in Sagstua.

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.