BIZTRAC BETA
Construction of residential and non-residential buildings

LF BYGG AS

Org. no. 831307412 Limited company (AS) Halden Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 509,000
Equity NOK 885,000
Incorporated 2023
Employees 7
Share capital NOK 30,000

LF BYGG AS is registered as a limited company in Halden, Østfold with organisation number 831307412. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tømrer og snekkerarbeid og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 509,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK 509,000
Equity
NOK 885,000
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.9%
Good
Equity as a share of total capital

Who owns LF BYGG AS?

STORGATA EIENDOM HALDEN AS
LF BYGG AS
NOK 8.9m rev. · NOK 509,000 profit

LF BYGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LF BYGG AS

Who owns LF BYGG AS?

STORGATA EIENDOM HALDEN AS is the largest registered owner, with 45.0%.

What is the revenue of LF BYGG AS?

LF BYGG AS had revenue of NOK 8.9m in 2025.

Who is the general manager of LF BYGG AS?

Lars Gran is registered as general manager of LF BYGG AS.

Where is LF BYGG AS based?

LF BYGG AS has its business address in Halden.

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.