BIZTRAC BETA
General medical practice activities

BJØRN RAVLO AS

Org. no. 967996300 Limited company (AS) Porsgrunn Incorporated 1993 Active
Ownership graph ↗
Operating profit NOK −127,000
Equity NOK 5.8m
Incorporated 1993
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−127k kr).

BJØRN RAVLO AS is registered as a limited company in Porsgrunn, Telemark with organisation number 967996300. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1993. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å drive legepraksis, konsulentvirksomhet med spesialister innen medisin og annet helsearbeid, gjennomføre etterutdanning av samme type personell, og drive forskning. Selskapet kan drive med kjøp og salg av varer, eiendom, løsøre, transportmidler og verdipapirer. Selskapet kan også ved aksjetegning eller på andre måter delta i annen næring. ”.

Key figures · 2025

Operating profit
NOK −127,000
Equity
NOK 5.8m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns BJØRN RAVLO AS?

BJØRN RAVLO
BJØRN RAVLO AS
· NOK −127,000 profit

BJØRN RAVLO AS has 8 registered shareholders:

All shareholders and roles →

Which companies does BJØRN RAVLO AS own?

BJØRN RAVLO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRN RAVLO AS

Who owns BJØRN RAVLO AS?

BJØRN RAVLO is the largest registered owner, with 45.0%.

Who is the general manager of BJØRN RAVLO AS?

Bjørn Ravlo is registered as general manager of BJØRN RAVLO AS.

Where is BJØRN RAVLO AS based?

BJØRN RAVLO AS has its business address in Brevik.

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.