biztrac. BETA
COMPANY REGISTER PROFILE
923130365 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Research and experimental development on natural sciences and engineering

YRKESHYGIENE AS

Org. no. 923130365 Limited company (AS) Trondheim Incorporated 2019 Active
Revenue 2025 NOK 118,000
Operating profit NOK 25,000
Equity NOK 184,000
Incorporated 2019
Share capital NOK 150,000

YRKESHYGIENE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 923130365. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2019. Registered share capital is NOK 150,000, divided into 150000 shares. The company's stated purpose is: “Kunnskapsformidling, rådgivning og forskning innen yrkeshygiene.”. The most recent filed accounts, for the 2025 financial year, show NOK 118,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 118,000
▼ −35 %
Operating profit
NOK 25,000
▲ +66 %
Equity
NOK 184,000
▲ +12 %
Est. value
NOK 218,000

Financial health · 2025

Liquidity
2.82
Very good
Current assets ÷ current liabilities
Profitability
9.1%
Satisfactory
Return on total assets
Solidity
64.7%
Very good
Equity as a share of total capital

Who owns YRKESHYGIENE AS?

YRKESHYGIENE AS
NOK 118,000 rev. · NOK 25,000 profit

YRKESHYGIENE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about YRKESHYGIENE AS

Who owns YRKESHYGIENE AS?

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

What is the revenue of YRKESHYGIENE AS?

YRKESHYGIENE AS had revenue of NOK 118,000 in 2025.

Who is the general manager of YRKESHYGIENE AS?

Hans Thore Smedbold is registered as general manager of YRKESHYGIENE AS.

Where is YRKESHYGIENE AS based?

YRKESHYGIENE AS has its business address in Trondheim.

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.