biztrac. BETA
COMPANY REGISTER PROFILE
913477812 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Preventive health care activities

KOMPLETT HMS DRIFT AS

Org. no. 913477812 Limited company (AS) Bergen Incorporated 2014 Active
Revenue 2025 NOK 5.3m
Operating profit NOK 838,000
Equity NOK 521,000
Incorporated 2014
Employees 10
Share capital NOK 30,000

KOMPLETT HMS DRIFT AS is registered as a limited company in Bergen, Vestland with organisation number 913477812. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2014 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikling av kvalitetssystemer og HMS systemer sentralgodkjenning og veiledning i byggesaker. Samt rådgiver og hjelpe bygg og anleggsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 838,000 in operating profit.

Former names: MER MEDIA AS, HMS VAKTEN AS

Key figures · 2025

Revenue
NOK 5.3m
▲ +2 %
Operating profit
NOK 838,000
▲ +130 %
Equity
NOK 521,000
▲ +489 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
1.20
Satisfactory
Current assets ÷ current liabilities
Profitability
58.0%
Very good
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns KOMPLETT HMS DRIFT AS?

KOMPLETT HMS DRIFT AS
NOK 5.3m rev. · NOK 838,000 profit

KOMPLETT HMS DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOMPLETT HMS DRIFT AS

Who owns KOMPLETT HMS DRIFT AS?

JALMS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KOMPLETT HMS DRIFT AS?

KOMPLETT HMS DRIFT AS had revenue of NOK 5.3m in 2025.

Where is KOMPLETT HMS DRIFT AS based?

KOMPLETT HMS DRIFT 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.