biztrac. BETA
COMPANY REGISTER PROFILE
931615696 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other education activities

ALIVENESS LAB AS

Org. no. 931615696 Limited company (AS) Stjørdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 288,000
Operating profit NOK 78,000
Equity NOK 101,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-09-22 Adresseendring registrert 2026-09-22.

ALIVENESS LAB AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 931615696. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Undervisning innen mental og fysisk helse.”. The most recent filed accounts, for the 2025 financial year, show NOK 288,000 in revenue and NOK 78,000 in operating profit.

Key figures · 2025

Revenue
NOK 288,000
▼ −29 %
Operating profit
NOK 78,000
▲ +288 %
Equity
NOK 101,000
▲ +228 %
Est. value
NOK 257,000

Financial health · 2025

Liquidity
13.95
Very good
Current assets ÷ current liabilities
Profitability
88.3%
Very good
Return on total assets
Solidity
92.8%
Very good
Equity as a share of total capital

Who owns ALIVENESS LAB AS?

ALIVENESS LAB AS
NOK 288,000 rev. · NOK 78,000 profit

ALIVENESS LAB AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALIVENESS LAB AS

Who owns ALIVENESS LAB AS?

Maiken Sneeggen is the largest registered owner, with 80.0%.

What is the revenue of ALIVENESS LAB AS?

ALIVENESS LAB AS had revenue of NOK 288,000 in 2025.

Who is the general manager of ALIVENESS LAB AS?

Maiken Sneeggen is registered as general manager of ALIVENESS LAB AS.

Where is ALIVENESS LAB AS based?

ALIVENESS LAB AS has its business address in Stjørdal.

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.