biztrac. BETA
COMPANY REGISTER PROFILE
933755029 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

EMMO SAFETY ENGINEERING AS

Org. no. 933755029 Limited company (AS) Lier Incorporated 1983 Active
Operating profit NOK −2,000
Equity NOK −199,000
Incorporated 1983
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−199k kr).

EMMO SAFETY ENGINEERING AS is registered as a limited company in Lier, Buskerud with organisation number 933755029. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1983. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive konsulentvirksomhet, investering, handel og annen i naturlig sammenheng forekommende virksomhet.”.

Former names: EMMO ENDOSKOPI AS

Key figures · 2025

Operating profit
NOK −2,000
▲ +71 %
Equity
NOK −199,000
▼ −1 %

Financial health · 2025

Liquidity
0.13
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-657.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns EMMO SAFETY ENGINEERING AS?

EMMO SAFETY ENGINEERING AS
· NOK −2,000 profit

EMMO SAFETY ENGINEERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EMMO SAFETY ENGINEERING AS

Who owns EMMO SAFETY ENGINEERING AS?

Jørund Osnes is the largest registered owner, with 100.0%.

Who is the general manager of EMMO SAFETY ENGINEERING AS?

Jørund Osnes is registered as general manager of EMMO SAFETY ENGINEERING AS.

Where is EMMO SAFETY ENGINEERING AS based?

EMMO SAFETY ENGINEERING AS has its business address in Tranby.

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.