BIZTRAC BETA
Joinery installation

LUKASBYGG AS

Org. no. 920669654 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 369,000
Operating profit NOK 79,000
Equity NOK −1,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1k kr).

LUKASBYGG AS is registered as a limited company in Bergen, Vestland with organisation number 920669654. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Byggtjenester, interiør etterbehandling, maling, små transporttjenester og andre produkter/tjenester som naturlig hører til dette, herunder å delta.”. The most recent filed accounts, for the 2024 financial year, show NOK 369,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2024

Revenue
NOK 369,000
Operating profit
NOK 79,000
Equity
NOK −1,000
Est. value
NOK 394,000

Financial health · 2024

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

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

Who owns LUKASBYGG AS?

LUKASZ ROMAN LENCZEWSKI
LUKASBYGG AS
NOK 369,000 rev. · NOK 79,000 profit

LUKASBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUKASBYGG AS

Who owns LUKASBYGG AS?

LUKASZ ROMAN LENCZEWSKI is the largest registered owner, with 100.0%.

What is the revenue of LUKASBYGG AS?

LUKASBYGG AS had revenue of NOK 369,000 in 2024.

Who is the general manager of LUKASBYGG AS?

Lukasz Roman Lenczewski is registered as general manager of LUKASBYGG AS.

Where is LUKASBYGG AS based?

LUKASBYGG AS has its business address in Godvik.

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.