BIZTRAC BETA
Rental and operating of own or leased real estate

LLOYDS INVEST AS

Org. no. 995261790 Limited company (AS) Hole Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK −542,000
Equity NOK 8.5m
Incorporated 2010
Share capital NOK 10.2m

Signals

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

LLOYDS INVEST AS is registered as a limited company in Hole, Buskerud with organisation number 995261790. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2010. Registered share capital is NOK 10.2m, divided into 10238 shares. The company's stated purpose is: “Kjøpe, selge og drifte fast eiendom, samt yte konsulenttjenester innenfor fast eiendom. I tillegg skal selskapet kunne delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK −542,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK −542,000
Equity
NOK 8.5m
Est. value
NOK 7.9m

Financial health · 2025

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.7%
Good
Equity as a share of total capital

Who owns LLOYDS INVEST AS?

SAMEIET STORGT 1
LLOYDS INVEST AS
NOK 3.0m rev. · NOK −542,000 profit

LLOYDS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LLOYDS INVEST AS

Who owns LLOYDS INVEST AS?

SAMEIET STORGT 1 is the largest registered owner, with 100.0%.

What is the revenue of LLOYDS INVEST AS?

LLOYDS INVEST AS had revenue of NOK 3.0m in 2025.

Who is the general manager of LLOYDS INVEST AS?

Per Gjerdrum Aasen is registered as general manager of LLOYDS INVEST AS.

Where is LLOYDS INVEST AS based?

LLOYDS INVEST AS has its business address in Røyse.

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.