biztrac. BETA
COMPANY REGISTER PROFILE
893345752 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

MILJØ AS

Org. no. 893345752 Limited company (AS) Namsos Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −475,000
Equity NOK 8.9m
Incorporated 2008
Share capital NOK 600,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−475k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-08-11 Adresseendring registrert 2026-08-11.

MILJØ AS is registered as a limited company in Namsos, Trøndelag with organisation number 893345752. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2008. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investeringer i fast eiendom og det som naturlig hører til. Videre kan selskapets virksomhet omfatte utleie og arrangement basert på friluftsopplevelser.”.

Former names: FOLK AS

Key figures · 2025

Operating profit
NOK −475,000
▼ −970 %
Equity
NOK 8.9m
▲ +0 %
Est. value
NOK 4.6m

Financial health · 2025

Liquidity
1556.67
Very good
Current assets ÷ current liabilities
Profitability
8.8%
Satisfactory
Return on total assets
Solidity
98.0%
Very good
Equity as a share of total capital

Who owns MILJØ AS?

MILJØ AS
· NOK −475,000 profit

MILJØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MILJØ AS own?

MILJØ AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about MILJØ AS

Who owns MILJØ AS?

Odd Magnar Fjellet is the largest registered owner, with 100.0%.

Where is MILJØ AS based?

MILJØ AS has its business address in Namsos.

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.