BIZTRAC BETA
Development of building projects

LILLEBY & MIKKELSEN INVEST AS

Org. no. 925129240 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −38,000
Equity NOK −29,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−29k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−38k kr).

LILLEBY & MIKKELSEN INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925129240. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 2 shares. The company's stated purpose is: “Forvaltning av eierinteresser og det som måtte stå i den forbindelse.”.

Key figures · 2024

Operating profit
NOK −38,000
Equity
NOK −29,000

Financial health · 2024

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

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

Who owns LILLEBY & MIKKELSEN INVEST AS?

Bård Magnus Mikkelsen
LILLEBY & MIKKELSEN INVEST AS
· NOK −38,000 profit

LILLEBY & MIKKELSEN INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LILLEBY & MIKKELSEN INVEST AS own?

LILLEBY & MIKKELSEN INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

LILLEBY & MIKKELSEN INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about LILLEBY & MIKKELSEN INVEST AS

Who owns LILLEBY & MIKKELSEN INVEST AS?

Bård Magnus Mikkelsen is the largest registered owner, with 50.0%.

Where is LILLEBY & MIKKELSEN INVEST AS based?

LILLEBY & MIKKELSEN INVEST AS has its business address in Tiller.

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.