BIZTRAC BETA
Traditional, complementary and alternative medicine activities

LIER NAPRAPATKLINIKK AS

Org. no. 995488019 Limited company (AS) Lier Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 2.8m
Operating profit NOK 219,000
Equity NOK 536,000
Incorporated 2010
Share capital NOK 100,000

LIER NAPRAPATKLINIKK AS is registered as a limited company in Lier, Buskerud with organisation number 995488019. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Manuell medisinbehandling med bakgrunn i naprapati og alt som står i forbindelse med dette - herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.8m in revenue and NOK 219,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.8m
Operating profit
NOK 219,000
Equity
NOK 536,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.5%
Good
Equity as a share of total capital

Who owns LIER NAPRAPATKLINIKK AS?

FRODE HENNUM
LIER NAPRAPATKLINIKK AS
NOK 2.8m rev. · NOK 219,000 profit

LIER NAPRAPATKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIER NAPRAPATKLINIKK AS

Who owns LIER NAPRAPATKLINIKK AS?

FRODE HENNUM is the largest registered owner, with 50.0%.

What is the revenue of LIER NAPRAPATKLINIKK AS?

LIER NAPRAPATKLINIKK AS had revenue of NOK 2.8m in 2024.

Who is the general manager of LIER NAPRAPATKLINIKK AS?

Frode Hennum is registered as general manager of LIER NAPRAPATKLINIKK AS.

Where is LIER NAPRAPATKLINIKK AS based?

LIER NAPRAPATKLINIKK AS has its business address in Lier.

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.