BIZTRAC BETA
Joinery installation

LØVSTUEN DRIFT AS

Org. no. 927235838 Limited company (AS) Nore Og Uvdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 192,000
Operating profit NOK 53,000
Equity NOK 186,000
Incorporated 2021
Share capital NOK 30,000

LØVSTUEN DRIFT AS is registered as a limited company in Nore Og Uvdal, Buskerud with organisation number 927235838. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive med kjøp, salg, utvikling og drift av fast eiendom og tjenester, brøyting, transport, graving, snekkerarbeid og annen lignende virksomhet, og å eie og delta i andre virksomheter og alt som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 192,000 in revenue and NOK 53,000 in operating profit.

Key figures · 2024

Revenue
NOK 192,000
Operating profit
NOK 53,000
Equity
NOK 186,000
Est. value
NOK 233,000

Financial health · 2024

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

Who owns LØVSTUEN DRIFT AS?

TOR LØVSTUEN
LØVSTUEN DRIFT AS
NOK 192,000 rev. · NOK 53,000 profit

LØVSTUEN DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVSTUEN DRIFT AS

Who owns LØVSTUEN DRIFT AS?

TOR LØVSTUEN is the largest registered owner, with 100.0%.

What is the revenue of LØVSTUEN DRIFT AS?

LØVSTUEN DRIFT AS had revenue of NOK 192,000 in 2024.

Who is the general manager of LØVSTUEN DRIFT AS?

Tor Løvstuen is registered as general manager of LØVSTUEN DRIFT AS.

Where is LØVSTUEN DRIFT AS based?

LØVSTUEN DRIFT AS has its business address in Uvdal.

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.