BIZTRAC BETA
Uoppgitt

SPAREBANK 1 MOBILITET HOLDING 2 AS

Org. no. 833039342 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 100,000
Incorporated 2023
Share capital NOK 100,000

Signals

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

SPAREBANK 1 MOBILITET HOLDING 2 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 833039342. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i virksomhet innen mobilitetsområdet samt det som naturlig står 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 100,000
Est. value
NOK 118,000

Financial health · 2024

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

Who owns SPAREBANK 1 MOBILITET HOLDING 2 AS?

SPAREBANK 1 SMN
SPAREBANK 1 MOBILITET HOLDING 2 AS
NOK 0 rev. · NOK 0 profit

SPAREBANK 1 MOBILITET HOLDING 2 AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPAREBANK 1 MOBILITET HOLDING 2 AS

Who owns SPAREBANK 1 MOBILITET HOLDING 2 AS?

SPAREBANK 1 SMN is the largest registered owner, with 56.5%.

What is the revenue of SPAREBANK 1 MOBILITET HOLDING 2 AS?

SPAREBANK 1 MOBILITET HOLDING 2 AS had revenue of NOK 0 in 2024.

Where is SPAREBANK 1 MOBILITET HOLDING 2 AS based?

SPAREBANK 1 MOBILITET HOLDING 2 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.