BIZTRAC BETA
Other captive investment companies

SWIFT INVEST AS

Org. no. 989215957 Limited company (AS) Steinkjer Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 2.6m
Equity NOK 56.9m
Incorporated 2005
Share capital NOK 100,000

SWIFT INVEST AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 989215957. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selv, eller ved deltakelse i, eller i samarbeid med andre selskaper, å investere i aksjer, eiendom eller dertil hørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 2.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 2.6m
Equity
NOK 56.9m
Est. value
NOK 39.1m

Financial health · 2024

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

Who owns SWIFT INVEST AS?

RUNE ERLING OPDAHL
SWIFT INVEST AS
NOK 3.0m rev. · NOK 2.6m profit

SWIFT INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SWIFT INVEST AS own?

SWIFT INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SWIFT INVEST AS

Who owns SWIFT INVEST AS?

RUNE ERLING OPDAHL is the largest registered owner, with 100.0%.

What is the revenue of SWIFT INVEST AS?

SWIFT INVEST AS had revenue of NOK 3.0m in 2024.

Who is the general manager of SWIFT INVEST AS?

Rune Erling Opdahl is registered as general manager of SWIFT INVEST AS.

Where is SWIFT INVEST AS based?

SWIFT INVEST AS has its business address in Steinkjer.

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.