BIZTRAC BETA
Civil engineering activities

LAUVBRO AS

Org. no. 917840547 Limited company (AS) Gran Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 7,000
Operating profit NOK −45,000
Equity NOK 697,000
Incorporated 2016
Share capital NOK 100,000

Signals

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

LAUVBRO AS is registered as a limited company in Gran, Innlandet with organisation number 917840547. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenester innen byggfag, prosjektere, bygge, vedlikeholde, eie og utvikle eiendom, samt andre produkter og tjenester som hører naturlig sammen med dette. Investere i aksjer, verdipapirer og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 7,000
Operating profit
NOK −45,000
Equity
NOK 697,000
Est. value
NOK 347,000

Financial health · 2024

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

Who owns LAUVBRO AS?

OLE ANDERS LØVBRØTTE
LAUVBRO AS
NOK 7,000 rev. · NOK −45,000 profit

LAUVBRO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAUVBRO AS own?

LAUVBRO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LAUVBRO AS

Who owns LAUVBRO AS?

OLE ANDERS LØVBRØTTE is the largest registered owner, with 100.0%.

What is the revenue of LAUVBRO AS?

LAUVBRO AS had revenue of NOK 7,000 in 2024.

Where is LAUVBRO AS based?

LAUVBRO AS has its business address in Jaren.

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.