BIZTRAC BETA
Construction of residential and non-residential buildings

LONE BYGG AS

Org. no. 922533210 Limited company (AS) Osterøy Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −68,000
Equity NOK 73,000
Incorporated 2019
Share capital NOK 80,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−68k kr).

LONE BYGG AS is registered as a limited company in Osterøy, Vestland with organisation number 922533210. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 80,000, divided into 80000 shares. The company's stated purpose is: “Oppføring av bygg. Kjøp og salg av byggevare, Vaktmestertjenester og lignende”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −68,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −68,000
Equity
NOK 73,000
Est. value
NOK 884,000

Financial health · 2025

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

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

Who owns LONE BYGG AS?

DANIEL LØTVEIT LONE
LONE BYGG AS
NOK 2.4m rev. · NOK −68,000 profit

LONE BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LONE BYGG AS

Who owns LONE BYGG AS?

DANIEL LØTVEIT LONE is the largest registered owner, with 50.0%.

What is the revenue of LONE BYGG AS?

LONE BYGG AS had revenue of NOK 2.4m in 2025.

Who is the general manager of LONE BYGG AS?

Daniel Løtveit Lone is registered as general manager of LONE BYGG AS.

Where is LONE BYGG AS based?

LONE BYGG AS has its business address in Lonevåg.

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.