BIZTRAC BETA
Rental and operating of own or leased real estate

FABRIKKVEIEN II AS

Org. no. 991659129 Limited company (AS) Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 10.4m
Operating profit NOK 9.0m
Equity NOK 14.2m
Incorporated 2007
Share capital NOK 100,000

FABRIKKVEIEN II AS is registered as a limited company in Hå, Rogaland with organisation number 991659129. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Investering i eiendom, herunder å eie eiendommen med adresse Fabrikkveien 1 på Vigrestad, investering i verdipapirer samt annet.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.4m in revenue and NOK 9.0m in operating profit.

Key figures · 2025

Revenue
NOK 10.4m
Operating profit
NOK 9.0m
Equity
NOK 14.2m
Est. value
NOK 27.8m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.3%
Very good
Equity as a share of total capital

Who owns FABRIKKVEIEN II AS?

AARSLAND HOLDING AS
FABRIKKVEIEN II AS
NOK 10.4m rev. · NOK 9.0m profit

FABRIKKVEIEN II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FABRIKKVEIEN II AS er morselskap for 6 datterselskaper:

Frequently asked questions about FABRIKKVEIEN II AS

Who owns FABRIKKVEIEN II AS?

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

What is the revenue of FABRIKKVEIEN II AS?

FABRIKKVEIEN II AS had revenue of NOK 10.4m in 2025.

Who is the general manager of FABRIKKVEIEN II AS?

Erik Jonas Aarsland is registered as general manager of FABRIKKVEIEN II AS.

Where is FABRIKKVEIEN II AS based?

FABRIKKVEIEN II AS has its business address in Vigrestad.

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.