BIZTRAC BETA
COMPANY REGISTER PROFILE
923258450 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

FFARG AS

Org. no. 923258450 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 146,000
Incorporated 2019
Share capital NOK 40,000

Signals

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

FFARG AS is registered as a limited company in Oslo, Oslo with organisation number 923258450. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 40,000, divided into 80 shares. The company's stated purpose is: “Investeringsselskap.”.

Key figures · 2025

Operating profit
NOK −5,000
▼ −71 %
Equity
NOK 146,000
▲ +116 %
Est. value
NOK 595,000

Financial health · 2025

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

Who owns FFARG AS?

FFARG AS
· NOK −5,000 profit

FFARG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FFARG AS own?

FFARG AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about FFARG AS

Who owns FFARG AS?

LINE GRAFF NESSE is the largest registered owner, with 100.0%.

Where is FFARG AS based?

FFARG AS has its business address in Oslo.

Property

Business address c/o Line Graff Nesse Gråkamveien 14B, 0779 Oslo
Cadastral unit 301-41/164/0/0
Building Stort frittliggende boligbygg på 3 og 4 etg · 20 units

10 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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