BIZTRAC BETA
Uoppgitt

SAGA FINANS AS

Org. no. 914554594 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK −69,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−69k kr).
  • Nylig endring 2026-05-06 Adresseendring registrert 2026-05-06.

SAGA FINANS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914554594. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “På en eller annen måte delta i andre selskaper, herunder kjøp og salg av aksjer. Og kunne utføre tjenester i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −69,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns SAGA FINANS AS?

ERLING RØNNING
SAGA FINANS AS
NOK 0 rev. · NOK 0 profit

SAGA FINANS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAGA FINANS AS

Who owns SAGA FINANS AS?

ERLING RØNNING is the largest registered owner, with 100.0%.

What is the revenue of SAGA FINANS AS?

SAGA FINANS AS had revenue of NOK 0 in 2024.

Who is the general manager of SAGA FINANS AS?

Fabian Patrick Westgård Johannessen is registered as general manager of SAGA FINANS AS.

Where is SAGA FINANS AS based?

SAGA FINANS AS has its business address in Trondheim.

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.