BIZTRAC BETA
Intermediation service activities for specialised retail sale

MØLJEN AS

Org. no. 828950282 Limited company (AS) Lørenskog Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 399,000
Operating profit NOK 302,000
Equity NOK 732,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MØLJEN AS is registered as a limited company in Lørenskog, Akershus with organisation number 828950282. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg og reparasjoner av kjøretøyer, båt, eiendom samt alt som derved står i naturlig forbindelse med dette. I tillegg utføres vaktmestertjenester, kontortjenester og det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 399,000 in revenue and NOK 302,000 in operating profit.

Key figures · 2025

Revenue
NOK 399,000
Operating profit
NOK 302,000
Equity
NOK 732,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns MØLJEN AS?

MØLLER & JENSEN EIENDOM AS
MØLJEN AS
NOK 399,000 rev. · NOK 302,000 profit

MØLJEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MØLJEN AS

Who owns MØLJEN AS?

MØLLER & JENSEN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of MØLJEN AS?

MØLJEN AS had revenue of NOK 399,000 in 2025.

Where is MØLJEN AS based?

MØLJEN AS has its business address in Rasta.

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.