BIZTRAC BETA
Security and commodity contracts brokerage

FINANSCO AS

Org. no. 996853586 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 60.3m
Operating profit NOK 7.1m
Equity NOK 25.7m
Incorporated 2011
Employees 19
Share capital NOK 104,000

FINANSCO AS is registered as a limited company in Oslo, Oslo with organisation number 996853586. The business is classified under security and commodity contracts brokerage (NACE 66.120). The company was incorporated in 2011 and has 19 registered employees. Registered share capital is NOK 104,000, divided into 1041667 shares. The company's stated purpose is: “Selskapets virksomhet er å yte investeringstjenestene nevnt i lov av 29. juni 2007 nr. 75 om verdipapirhandel § 2-1 (1) nr. 4 og 5, og den tilknyttede tjenesten nevnt i samme lov § 2-1 (2) nr. 5, samt alt som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 60.3m in revenue and NOK 7.1m in operating profit.

Key figures · 2025

Revenue
NOK 60.3m
Operating profit
NOK 7.1m
Equity
NOK 25.7m
Est. value
NOK 38.0m

Financial health · 2025

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

Who owns FINANSCO AS?

FINANSCO HOLDING AS
FINANSCO AS
NOK 60.3m rev. · NOK 7.1m profit

FINANSCO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FINANSCO AS

Who owns FINANSCO AS?

FINANSCO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of FINANSCO AS?

FINANSCO AS had revenue of NOK 60.3m in 2025.

Who is the general manager of FINANSCO AS?

Eirik Losgård Landheim is registered as general manager of FINANSCO AS.

Where is FINANSCO AS based?

FINANSCO 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.