biztrac. BETA
COMPANY REGISTER PROFILE
989719238 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Physiotherapy activities

SPRELL LEVENDE AS

Org. no. 989719238 Limited company (AS) Lørenskog Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −429,000
Incorporated 2006
Share capital NOK 946,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−429k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

SPRELL LEVENDE AS is registered as a limited company in Lørenskog, Akershus with organisation number 989719238. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2006. Registered share capital is NOK 946,000, divided into 946 shares. The company's stated purpose is: “Forebyggende helsearbeid, utøve praksis innen fysioterapi, trenings- og aktivitetsgrupper, foredrag/undervisning om fysisk aktivitet og bevegelsesutvikling mm, konsulenttjenester, samt deltagelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −14,000
▲ +30 %
Equity
NOK −429,000
▼ −3 %

Financial health · 2025

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

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

Who owns SPRELL LEVENDE AS?

SPRELL LEVENDE AS
· NOK −14,000 profit

SPRELL LEVENDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SPRELL LEVENDE AS

Who owns SPRELL LEVENDE AS?

Hege Heiestad is the largest registered owner, with 100.0%.

Who is the general manager of SPRELL LEVENDE AS?

Hege Heiestad is registered as general manager of SPRELL LEVENDE AS.

Where is SPRELL LEVENDE AS based?

SPRELL LEVENDE AS has its business address in Fjellhamar.

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.