BIZTRAC BETA
Other technical consultancy

RONNEBERG MEDICAL AUDITING AS

Org. no. 931848623 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 868,000
Equity NOK 737,000
Incorporated 2023
Share capital NOK 30,000

RONNEBERG MEDICAL AUDITING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 931848623. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kvalitetsrevisjon mot produsenter av medisinsk utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 868,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 868,000
Equity
NOK 737,000
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns RONNEBERG MEDICAL AUDITING AS?

VILLY ØYSTEIN RØNNEBERG
RONNEBERG MEDICAL AUDITING AS
NOK 2.2m rev. · NOK 868,000 profit

RONNEBERG MEDICAL AUDITING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RONNEBERG MEDICAL AUDITING AS

Who owns RONNEBERG MEDICAL AUDITING AS?

VILLY ØYSTEIN RØNNEBERG is the largest registered owner, with 100.0%.

What is the revenue of RONNEBERG MEDICAL AUDITING AS?

RONNEBERG MEDICAL AUDITING AS had revenue of NOK 2.2m in 2024.

Who is the general manager of RONNEBERG MEDICAL AUDITING AS?

Villy Øystein Rønneberg is registered as general manager of RONNEBERG MEDICAL AUDITING AS.

Where is RONNEBERG MEDICAL AUDITING AS based?

RONNEBERG MEDICAL AUDITING AS has its business address in Vear.

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.