BIZTRAC BETA
Preventive health care activities

EURO SAFETY AS

Org. no. 814527352 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK −960,000
Equity NOK 2.4m
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−960k kr).

EURO SAFETY AS is registered as a limited company in Stavanger, Rogaland with organisation number 814527352. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Holde foredrag innen helse, miljø og sikkerhet. Selskapet vil også forestå investering i annen næringsvirksomhet, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK −960,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK −960,000
Equity
NOK 2.4m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns EURO SAFETY AS?

TERJE BJØRKEVOLL
EURO SAFETY AS
NOK 46,000 rev. · NOK −960,000 profit

EURO SAFETY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EURO SAFETY AS own?

EURO SAFETY AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about EURO SAFETY AS

Who owns EURO SAFETY AS?

TERJE BJØRKEVOLL is the largest registered owner, with 100.0%.

What is the revenue of EURO SAFETY AS?

EURO SAFETY AS had revenue of NOK 46,000 in 2024.

Where is EURO SAFETY AS based?

EURO SAFETY AS has its business address in Hundvåg.

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.