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

LILLEÅS EIENDOMSINVEST AS

Org. no. 931774778 Limited company (AS) Kongsberg Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 0
Incorporated 2023
Share capital NOK 30,000

LILLEÅS EIENDOMSINVEST AS is registered as a limited company in Kongsberg, Buskerud with organisation number 931774778. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp/salg/utleie av eiendom.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 0

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns LILLEÅS EIENDOMSINVEST AS?

LILLEÅS EIENDOMSINVEST AS
· NOK 0 profit

LILLEÅS EIENDOMSINVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLEÅS EIENDOMSINVEST AS

Who owns LILLEÅS EIENDOMSINVEST AS?

Marius Lilleås is the largest registered owner, with 100.0%.

Where is LILLEÅS EIENDOMSINVEST AS based?

LILLEÅS EIENDOMSINVEST AS has its business address in Skollenborg.

Property

Business address Efteløtmoen 18, 3618 Skollenborg
Cadastral unit 3303-45/63/0/0
Building Enebolig · 1 unit

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.