biztrac. BETA
COMPANY REGISTER PROFILE
998870046 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of specialist physicians, other than psychiatrists

LIFE BEAT NORGE AS

Org. no. 998870046 Limited company (AS) Bergen Incorporated 2012 Active
Revenue 2025 NOK 3.8m
Operating profit NOK 3.8m
Equity NOK −3.5m
Incorporated 2012
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,5 mill kr).

LIFE BEAT NORGE AS is registered as a limited company in Bergen, Vestland with organisation number 998870046. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Etablering og drift av legetjeneste, etablering av en røntgen senter.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 3.8m in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 3.8m
▲ +23713 %
Equity
NOK −3.5m
▲ +52 %
Est. value
NOK 10.6m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
13587.2%
Very good
Return on total assets
Solidity
-12485.6%
Weak
Equity as a share of total capital

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

Who owns LIFE BEAT NORGE AS?

LIFE BEAT NORGE AS
NOK 3.8m rev. · NOK 3.8m profit

LIFE BEAT NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIFE BEAT NORGE AS

Who owns LIFE BEAT NORGE AS?

PLASMACUTE AS is the largest registered owner, with 100.0%.

What is the revenue of LIFE BEAT NORGE AS?

LIFE BEAT NORGE AS had revenue of NOK 3.8m in 2025.

Where is LIFE BEAT NORGE AS based?

LIFE BEAT NORGE AS has its business address in Bergen.

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.