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

FRIERGANGEN 3 AS

Org. no. 979414722 Limited company (AS) Arendal Incorporated 1997 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 48,000
Incorporated 1997
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).
  • Nylig endring 2026-10-02 Adresseendring registrert 2026-10-02.

FRIERGANGEN 3 AS is registered as a limited company in Arendal, Agder with organisation number 979414722. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Kjøp og salg og utvikling av eiendom, samt alt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”.

Former names: HAVANA TRAVEL AS

Key figures · 2025

Operating profit
NOK −9,000
▼ −16 %
Equity
NOK 48,000
▼ −15 %
Est. value
NOK 44,000

Financial health · 2025

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
25.8%
Weak
Equity as a share of total capital

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

Who owns FRIERGANGEN 3 AS?

FRIERGANGEN 3 AS
· NOK −9,000 profit

FRIERGANGEN 3 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRIERGANGEN 3 AS

Who owns FRIERGANGEN 3 AS?

ARENDAL KOMMUNALE PENSJONSKASSE is the largest registered owner, with 100.0%.

Who is the general manager of FRIERGANGEN 3 AS?

Kjetil Korneliussen is registered as general manager of FRIERGANGEN 3 AS.

Where is FRIERGANGEN 3 AS based?

FRIERGANGEN 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 03.10.2026.

Report a problem

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