BIZTRAC BETA
Other health services

LIMICEPH AS

Org. no. 931540467 Limited company (AS) Asker Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 348,000
Operating profit NOK 139,000
Equity NOK −352,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

LIMICEPH AS is registered as a limited company in Asker, Akershus with organisation number 931540467. The business is classified under other health services (NACE 86.993). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Utvikle, tilby og selge tjenester og produkter innen diagnostikk, behandling og forebygging av smerte, funksjonsnedsettelse, svimmelhet, hodepine og beslektede områder.”. The most recent filed accounts, for the 2025 financial year, show NOK 348,000 in revenue and NOK 139,000 in operating profit.

Key figures · 2025

Revenue
NOK 348,000
Operating profit
NOK 139,000
Equity
NOK −352,000
Est. value
NOK 601,000

Financial health · 2025

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

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

Who owns LIMICEPH AS?

HELSE I ALLE LEDD AS
LIMICEPH AS
NOK 348,000 rev. · NOK 139,000 profit

LIMICEPH AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIMICEPH AS

Who owns LIMICEPH AS?

HELSE I ALLE LEDD AS is the largest registered owner, with 90.0%.

What is the revenue of LIMICEPH AS?

LIMICEPH AS had revenue of NOK 348,000 in 2025.

Who is the general manager of LIMICEPH AS?

Martin Herneblad-Due is registered as general manager of LIMICEPH AS.

Where is LIMICEPH AS based?

LIMICEPH AS has its business address in Asker.

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.