BIZTRAC BETA
Business and other management consultancy activities

TROPHY & MAC AS

Org. no. 914004233 Limited company (AS) Bodø Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 97,000
Operating profit NOK 35,000
Equity NOK 71,000
Incorporated 2014
Share capital NOK 30,000

TROPHY & MAC AS is registered as a limited company in Bodø, Nordland with organisation number 914004233. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester og prosjektledelse. Selskapet kan levere konsulentoppdrag. Selskapet kan lede prosjekter på oppdrag. Selskapet kan iverksette og eie egne prosjekter. Selskapet kan erverve bygg og anlegg som kreves for å gjennomføre oppdrag og prosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 97,000 in revenue and NOK 35,000 in operating profit.

Key figures · 2025

Revenue
NOK 97,000
Operating profit
NOK 35,000
Equity
NOK 71,000
Est. value
NOK 156,000

Financial health · 2024

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

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

Who owns TROPHY & MAC AS?

ØYVIND STENBERG LIEN IVERSEN
TROPHY & MAC AS
NOK 97,000 rev. · NOK 35,000 profit

TROPHY & MAC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROPHY & MAC AS

Who owns TROPHY & MAC AS?

ØYVIND STENBERG LIEN IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of TROPHY & MAC AS?

TROPHY & MAC AS had revenue of NOK 97,000 in 2025.

Where is TROPHY & MAC AS based?

TROPHY & MAC AS has its business address in Bodø.

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.