BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

TALISMAN CONSULTING AS

Org. no. 990687374 Limited company (AS) Haugesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1,000
Operating profit NOK −19,000
Equity NOK 756,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

TALISMAN CONSULTING AS is registered as a limited company in Haugesund, Rogaland with organisation number 990687374. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investerings- og konsulentvirksomhet, handel, eiendomsdrift og alt som står i forbindelse med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 1,000
Operating profit
NOK −19,000
Equity
NOK 756,000
Est. value
NOK 370,000

Financial health · 2025

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

Who owns TALISMAN CONSULTING AS?

KÅRE FRANSETH
TALISMAN CONSULTING AS
NOK 1,000 rev. · NOK −19,000 profit

TALISMAN CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TALISMAN CONSULTING AS

Who owns TALISMAN CONSULTING AS?

KÅRE FRANSETH is the largest registered owner, with 100.0%.

What is the revenue of TALISMAN CONSULTING AS?

TALISMAN CONSULTING AS had revenue of NOK 1,000 in 2025.

Where is TALISMAN CONSULTING AS based?

TALISMAN CONSULTING AS has its business address in Haugesund.

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.