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

PREG HARSTAD AS

Org. no. 889746602 Limited company (AS) Harstad Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 492,000
Equity NOK 2.3m
Incorporated 2006
Share capital NOK 900,000

PREG HARSTAD AS is registered as a limited company in Harstad, Troms with organisation number 889746602. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 900,000, divided into 900 shares. The company's stated purpose is: “Å drive eiendomsutvikling, arealutleie, investeringer og alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 492,000 in operating profit.

Former names: FOKUS AREAL AS, IQBEN AS

Key figures · 2025

Revenue
NOK 2.1m
▲ +0 %
Operating profit
NOK 492,000
▲ +37 %
Equity
NOK 2.3m
▼ −2 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
4.3%
Weak
Return on total assets
Solidity
20.4%
Good
Equity as a share of total capital

Who owns PREG HARSTAD AS?

PREG HARSTAD AS
NOK 2.1m rev. · NOK 492,000 profit

PREG HARSTAD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PREG HARSTAD AS

Who owns PREG HARSTAD AS?

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

What is the revenue of PREG HARSTAD AS?

PREG HARSTAD AS had revenue of NOK 2.1m in 2025.

Who is the general manager of PREG HARSTAD AS?

Håvard Inge Tømmerås is registered as general manager of PREG HARSTAD AS.

Where is PREG HARSTAD AS based?

PREG HARSTAD AS has its business address in Harstad.

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.