BIZTRAC BETA
COMPANY REGISTER PROFILE
889061782 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

FERSKEN INVEST AS

Org. no. 889061782 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 12,000
Operating profit NOK −4,000
Equity NOK 5.3m
Incorporated 2005
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

FERSKEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 889061782. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet skal bestå i å eie andeler i andre selskaper, investere i norske og utenlandske verdipapirer, eiendommer mv og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 12,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 12,000
Operating profit
NOK −4,000
Equity
NOK 5.3m
Est. value
NOK 3.7m

Financial health · 2025

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

Who owns FERSKEN INVEST AS?

PETTER EILERTSEN
FERSKEN INVEST AS
NOK 12,000 rev. · NOK −4,000 profit

FERSKEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FERSKEN INVEST AS

Who owns FERSKEN INVEST AS?

PETTER EILERTSEN is the largest registered owner, with 100.0%.

What is the revenue of FERSKEN INVEST AS?

FERSKEN INVEST AS had revenue of NOK 12,000 in 2025.

Where is FERSKEN INVEST AS based?

FERSKEN INVEST 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.