BIZTRAC BETA
COMPANY REGISTER PROFILE
916613539 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Rental and operating of own or leased real estate

LILLINVEST AS

Org. no. 916613539 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 1.0m
Equity NOK 2.1m
Incorporated 2016
Share capital NOK 30,000

LILLINVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 916613539. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og andre verdipapirer, kjøp, utvikling og salg av fast eiendom, herunder deltakelse i andre selskaper og virksomheter, samt utførelse av ulike konsulent- og rådgivningsoppdrag.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 1.0m
Equity
NOK 2.1m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns LILLINVEST AS?

LILLINVEST AS
NOK 1.7m rev. · NOK 1.0m profit

LILLINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLINVEST AS

Who owns LILLINVEST AS?

TERJE LILLEMO is the largest registered owner, with 100.0%.

What is the revenue of LILLINVEST AS?

LILLINVEST AS had revenue of NOK 1.7m in 2025.

Who is the general manager of LILLINVEST AS?

Terje Lillemo is registered as general manager of LILLINVEST AS.

Where is LILLINVEST AS based?

LILLINVEST AS has its business address in Klæbu.

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

Report a problem

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