biztrac. BETA
COMPANY REGISTER PROFILE
936755739 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other health services

STOL PÅ TUVA AS

Org. no. 936755739 Limited company (AS) Moss Incorporated 2025 Active
Operating profit NOK −52,000
Equity NOK −28,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

STOL PÅ TUVA AS is registered as a limited company in Moss, Østfold with organisation number 936755739. The business is classified under other health services (NACE 86.993). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å tilby coaching, kognitiv terapi, samtaleterapi og andre forebyggende helsetjenester, undervisning og relaterte tjenester. Selskapet kan utvikle og selge digitale kurs, bøker, innhold, samt drive foredragsvirksomhet. Selskapet kan i tillegg foreta investeringer og delta i annen virksomhet som står i naturlig sammenheng med formålet.”.

Key figures · 2025

Operating profit
NOK −52,000
Equity
NOK −28,000

Financial health · 2025

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-75.3%
Weak
Equity as a share of total capital

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

Who owns STOL PÅ TUVA AS?

STOL PÅ TUVA AS
· NOK −52,000 profit

STOL PÅ TUVA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STOL PÅ TUVA AS

Who owns STOL PÅ TUVA AS?

Tuva Ludahl Iversen is the largest registered owner, with 100.0%.

Who is the general manager of STOL PÅ TUVA AS?

Tuva Ludahl Iversen is registered as general manager of STOL PÅ TUVA AS.

Where is STOL PÅ TUVA AS based?

STOL PÅ TUVA AS has its business address in Moss.

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.