BIZTRAC BETA
Rental and operating of own or leased real estate

FRIHOLMSGATE 3 AS

Org. no. 917242542 Limited company (AS) Arendal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 629,000
Operating profit NOK 217,000
Equity NOK 37,000
Incorporated 2016
Share capital NOK 30,000

FRIHOLMSGATE 3 AS is registered as a limited company in Arendal, Agder with organisation number 917242542. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av eiendom, samt andre aktiviteter som er naturlig i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 629,000 in revenue and NOK 217,000 in operating profit.

Key figures · 2025

Revenue
NOK 629,000
Operating profit
NOK 217,000
Equity
NOK 37,000
Est. value
NOK 443,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns FRIHOLMSGATE 3 AS?

ARENDAL BYUTVIKLING AS
FRIHOLMSGATE 3 AS
NOK 629,000 rev. · NOK 217,000 profit

FRIHOLMSGATE 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRIHOLMSGATE 3 AS

Who owns FRIHOLMSGATE 3 AS?

ARENDAL BYUTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of FRIHOLMSGATE 3 AS?

FRIHOLMSGATE 3 AS had revenue of NOK 629,000 in 2025.

Who is the general manager of FRIHOLMSGATE 3 AS?

Petter Aaland is registered as general manager of FRIHOLMSGATE 3 AS.

Where is FRIHOLMSGATE 3 AS based?

FRIHOLMSGATE 3 AS has its business address in Arendal.

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.