BIZTRAC BETA
Construction of residential and non-residential buildings

LILLØY BYGG AS

Org. no. 913811445 Limited company (AS) Skien Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK −59,000
Equity NOK 210,000
Incorporated 2014
Employees 7
Share capital NOK 30,000

Signals

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

LILLØY BYGG AS is registered as a limited company in Skien, Telemark with organisation number 913811445. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2014 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av tømrertjenester til næringslivet og det private markedet når det gjelder nybygg, renovering og vedlikehold.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK −59,000
Equity
NOK 210,000
Est. value
NOK 2.9m

Financial health · 2024

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

Who owns LILLØY BYGG AS?

LILLØY HOLDING AS
LILLØY BYGG AS
NOK 8.5m rev. · NOK −59,000 profit

LILLØY BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LILLØY BYGG AS

Who owns LILLØY BYGG AS?

LILLØY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LILLØY BYGG AS?

LILLØY BYGG AS had revenue of NOK 8.5m in 2024.

Who is the general manager of LILLØY BYGG AS?

Stian Lilløy is registered as general manager of LILLØY BYGG AS.

Where is LILLØY BYGG AS based?

LILLØY BYGG AS has its business address in Skien.

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.