biztrac. BETA
COMPANY REGISTER PROFILE
922158746 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

DRON EIENDOM AS

Org. no. 922158746 Limited company (AS) Sør-Varanger Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 500,000
Operating profit NOK 174,000
Equity NOK 289,000
Incorporated 2019
Share capital NOK 30,000

DRON EIENDOM AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 922158746. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av eiendom, samt utleie av eindom og annen næringsvirksomhet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 500,000 in revenue and NOK 174,000 in operating profit.

Key figures · 2025

Revenue
NOK 500,000
▼ −35 %
Operating profit
NOK 174,000
▼ −66 %
Equity
NOK 289,000
▼ −39 %
Est. value
NOK 754,000

Financial health · 2025

Liquidity
0.17
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.5%
Weak
Return on total assets
Solidity
4.0%
Weak
Equity as a share of total capital

Who owns DRON EIENDOM AS?

DRON EIENDOM AS
NOK 500,000 rev. · NOK 174,000 profit

DRON EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DRON EIENDOM AS

Who owns DRON EIENDOM AS?

DRON HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DRON EIENDOM AS?

DRON EIENDOM AS had revenue of NOK 500,000 in 2025.

Who is the general manager of DRON EIENDOM AS?

Robert Wille is registered as general manager of DRON EIENDOM AS.

Where is DRON EIENDOM AS based?

DRON EIENDOM AS has its business address in Jarfjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.