BIZTRAC BETA
Research and experimental development on natural sciences and engineering

MARINE ENVIRONMENT AS

Org. no. 932094800 Limited company (AS) Moss Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 23,000
Incorporated 2023
Share capital NOK 60,000

Signals

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

MARINE ENVIRONMENT AS is registered as a limited company in Moss, Østfold with organisation number 932094800. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 60 shares. The company's stated purpose is: “Utvikling av system samt importere og selge utstyr og gode løsninger for god havhelse, samt annet som står i naturlig forbindelse med dette. Drifte og vedlikeholde ulike vaske og rensesystem for marine farkoster. Investere i eiendom og andre selskap.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK 23,000
Est. value
NOK 37,000

Financial health · 2024

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

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

Who owns MARINE ENVIRONMENT AS?

JOHN HARJINDER SINGH
MARINE ENVIRONMENT AS
· NOK −9,000 profit

MARINE ENVIRONMENT AS has 2 registered shareholders:

All shareholders and roles →

Which companies does MARINE ENVIRONMENT AS own?

MARINE ENVIRONMENT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MARINE ENVIRONMENT AS

Who owns MARINE ENVIRONMENT AS?

JOHN HARJINDER SINGH is the largest registered owner, with 50.0%.

Where is MARINE ENVIRONMENT AS based?

MARINE ENVIRONMENT AS has its business address in Rygge.

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.