BIZTRAC BETA
Activities in reception centres for asylum seekers

LML AS

Org. no. 916940033 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 995,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

LML AS is registered as a limited company in Oslo, Oslo with organisation number 916940033. The business is classified under activities in reception centres for asylum seekers (NACE 87.992). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av asylmottak, anskaffelse og drift av eiendommer, eiendomsutvikling, konsulentvirksomhet, administrasjon og drift av omsorgs- og assistansevirksomhet rettet mot barne- og ungdomsinstitusjoner, eldresentre, dagsenter for barn, ungdom, handikappede og eldre, omsorgshjem og for ledsagertjenester deltagelse i andre virksomheter samt alt hva som står i forbindelse med ovennevnte herunder deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK 995,000
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns LML AS?

LJILJANA MEDIC
LML AS
· NOK −7,000 profit

LML AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LML AS own?

LML AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LML AS

Who owns LML AS?

LJILJANA MEDIC is the largest registered owner, with 100.0%.

Who is the general manager of LML AS?

Ljiljana Medic is registered as general manager of LML AS.

Where is LML AS based?

LML AS has its business address in Oslo.

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.