BIZTRAC BETA
Wholesale of metals and metal ores

ENVIRO OFFSHORE AS

Org. no. 927804549 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 59,000
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−23k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ENVIRO OFFSHORE AS is registered as a limited company in Holmestrand, Vestfold with organisation number 927804549. The business is classified under wholesale of metals and metal ores (NACE 46.820). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive virksomhet innenfor handel, produksjon og utvikling, eksport og agentvirksomhet, samt deltakelse i andre selskaper og tilhørende forvaltning, samt drive virksomhet som naturlig hører til dette.”.

Key figures · 2025

Operating profit
NOK −23,000
Equity
NOK 59,000
Est. value
NOK 74,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns ENVIRO OFFSHORE AS?

PG FLOW SOLUTIONS AS
ENVIRO OFFSHORE AS
· NOK −23,000 profit

ENVIRO OFFSHORE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ENVIRO OFFSHORE AS

Who owns ENVIRO OFFSHORE AS?

PG FLOW SOLUTIONS AS is the largest registered owner, with 100.0%.

Who is the general manager of ENVIRO OFFSHORE AS?

Roy Rødningen is registered as general manager of ENVIRO OFFSHORE AS.

Where is ENVIRO OFFSHORE AS based?

ENVIRO OFFSHORE AS has its business address in Sande I Vestfold.

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.