BIZTRAC BETA
COMPANY REGISTER PROFILE
912505308 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

L-M INVEST AS

Org. no. 912505308 Limited company (AS) Færder Incorporated 2013 Active
Ownership graph ↗
Equity NOK 400,000
Incorporated 2013
Share capital NOK 30,000

L-M INVEST AS is registered as a limited company in Færder, Vestfold with organisation number 912505308. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer og andeler samt tilhørende virksomhet. Investering i fast eiendom og eiendomsrelaterte prosjekter.”.

Key figures · 2025

Equity
NOK 400,000
Est. value
NOK 365,000

Financial health · 2025

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

Who owns L-M INVEST AS?

L-M INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does L-M INVEST AS own?

L-M INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about L-M INVEST AS

Who owns L-M INVEST AS?

MARIUS LILLE-MÆHLUM is the largest registered owner, with 100.0%.

Where is L-M INVEST AS based?

L-M INVEST AS has its business address in Tjøme.

Property

Business address C/O Marius Lille-Mæhlum Slottåsen 5, 3145 Tjøme
Cadastral unit 3911-217/29/0/0
Building Enebolig · 1 unit

8 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.