BIZTRAC BETA
Computer programming activities

SWAHN CONSULTING AS

Org. no. 919300817 Limited company (AS) Midtre Gauldal Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 66,000
Operating profit NOK −19,000
Equity NOK 144,000
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

SWAHN CONSULTING AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 919300817. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Programmering og tekniske tjenester. Investering i aksjer og øvrige verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 66,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 66,000
Operating profit
NOK −19,000
Equity
NOK 144,000
Est. value
NOK 176,000

Financial health · 2024

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

Who owns SWAHN CONSULTING AS?

ISAK MATTIAS SWAHN
SWAHN CONSULTING AS
NOK 66,000 rev. · NOK −19,000 profit

SWAHN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SWAHN CONSULTING AS own?

SWAHN CONSULTING AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about SWAHN CONSULTING AS

Who owns SWAHN CONSULTING AS?

ISAK MATTIAS SWAHN is the largest registered owner, with 100.0%.

What is the revenue of SWAHN CONSULTING AS?

SWAHN CONSULTING AS had revenue of NOK 66,000 in 2024.

Where is SWAHN CONSULTING AS based?

SWAHN CONSULTING AS has its business address in Støren.

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.