BIZTRAC BETA
Public relations and communication activities

WETRUVIAN SOLUTIONS AS

Org. no. 998535107 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9,000
Operating profit NOK −108,000
Equity NOK 3.7m
Incorporated 2012
Share capital NOK 30,000

Signals

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

WETRUVIAN SOLUTIONS AS is registered as a limited company in Oslo, Oslo with organisation number 998535107. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rådgivning og konsulenttjenester innen media.”. The most recent filed accounts, for the 2024 financial year, show NOK 9,000 in revenue and NOK −108,000 in operating profit.

Key figures · 2024

Revenue
NOK 9,000
Operating profit
NOK −108,000
Equity
NOK 3.7m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns WETRUVIAN SOLUTIONS AS?

EVEN GABRIELSEN WETTEN
WETRUVIAN SOLUTIONS AS
NOK 9,000 rev. · NOK −108,000 profit

WETRUVIAN SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WETRUVIAN SOLUTIONS AS own?

WETRUVIAN SOLUTIONS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about WETRUVIAN SOLUTIONS AS

Who owns WETRUVIAN SOLUTIONS AS?

EVEN GABRIELSEN WETTEN is the largest registered owner, with 100.0%.

What is the revenue of WETRUVIAN SOLUTIONS AS?

WETRUVIAN SOLUTIONS AS had revenue of NOK 9,000 in 2024.

Where is WETRUVIAN SOLUTIONS AS based?

WETRUVIAN SOLUTIONS 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.