BIZTRAC BETA
Public relations and communication activities

TAIGA STRATEGY AND COMMUNICATIONS AS

Org. no. 834343932 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

TAIGA STRATEGY AND COMMUNICATIONS AS is registered as a limited company in Oslo, Oslo with organisation number 834343932. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulent.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 19,000
Est. value
NOK 31,000

Financial health · 2024

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

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

Who owns TAIGA STRATEGY AND COMMUNICATIONS AS?

VICTOR JAMES PONSFORD
TAIGA STRATEGY AND COMMUNICATIONS AS
NOK 0 rev. · NOK −11,000 profit

TAIGA STRATEGY AND COMMUNICATIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAIGA STRATEGY AND COMMUNICATIONS AS

Who owns TAIGA STRATEGY AND COMMUNICATIONS AS?

VICTOR JAMES PONSFORD is the largest registered owner, with 100.0%.

What is the revenue of TAIGA STRATEGY AND COMMUNICATIONS AS?

TAIGA STRATEGY AND COMMUNICATIONS AS had revenue of NOK 0 in 2024.

Where is TAIGA STRATEGY AND COMMUNICATIONS AS based?

TAIGA STRATEGY AND COMMUNICATIONS AS has its business address in Oslo.

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.