BIZTRAC BETA
Construction of residential and non-residential buildings

LØVSETH BYGG AS

Org. no. 976507282 Limited company (AS) Steinkjer Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 4.1m
Operating profit NOK 482,000
Equity NOK 1.4m
Incorporated 1996
Share capital NOK 100,000

LØVSETH BYGG AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 976507282. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 33 shares. The company's stated purpose is: “Byggeentreprenørvirksomhet, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.1m in revenue and NOK 482,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.1m
Operating profit
NOK 482,000
Equity
NOK 1.4m
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.66
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.2%
Very good
Equity as a share of total capital

Who owns LØVSETH BYGG AS?

STIG RUNE LØVSETH
LØVSETH BYGG AS
NOK 4.1m rev. · NOK 482,000 profit

LØVSETH BYGG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØVSETH BYGG AS own?

LØVSETH BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LØVSETH BYGG AS

Who owns LØVSETH BYGG AS?

STIG RUNE LØVSETH is the largest registered owner, with 100.0%.

What is the revenue of LØVSETH BYGG AS?

LØVSETH BYGG AS had revenue of NOK 4.1m in 2025.

Who is the general manager of LØVSETH BYGG AS?

Stig Rune Løvseth is registered as general manager of LØVSETH BYGG AS.

Where is LØVSETH BYGG AS based?

LØVSETH BYGG AS has its business address in Malm.

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.