BIZTRAC BETA
Rental and operating of own or leased real estate

FRAM ARKEN AS

Org. no. 964722307 Limited company (AS) Oslo Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 91.9m
Operating profit NOK 67.5m
Equity NOK 341.6m
Incorporated 1992
Share capital NOK 280.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FRAM ARKEN AS is registered as a limited company in Oslo, Oslo with organisation number 964722307. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 280.0m, divided into 5000 shares. The company's stated purpose is: “Kjøp, salg, utleie og utvikling av fast eiendom, og hva som hermed står i forbindelse, samt investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 91.9m in revenue and NOK 67.5m in operating profit.

Key figures · 2024

Revenue
NOK 91.9m
Operating profit
NOK 67.5m
Equity
NOK 341.6m
Est. value
NOK 340.7m

Financial health · 2024

Liquidity
3.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.3%
Good
Equity as a share of total capital

Who owns FRAM ARKEN AS?

FRAM MANAGEMENT AS
FRAM ARKEN AS
NOK 91.9m rev. · NOK 67.5m profit

FRAM ARKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRAM ARKEN AS

Who owns FRAM ARKEN AS?

FRAM MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of FRAM ARKEN AS?

FRAM ARKEN AS had revenue of NOK 91.9m in 2024.

Who is the general manager of FRAM ARKEN AS?

Magnus Tvenge is registered as general manager of FRAM ARKEN AS.

Where is FRAM ARKEN AS based?

FRAM ARKEN AS has its business address in Oslo.

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.