BIZTRAC BETA
Activities of advertising agencies

FYRMESTER INVEST AS

Org. no. 927344459 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −31,000
Equity NOK 2,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

FYRMESTER INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 927344459. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie aksjer i andre selskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −31,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −31,000
Equity
NOK 2,000
Est. value
NOK 3,000

Financial health · 2024

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.1%
Weak
Equity as a share of total capital

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

Who owns FYRMESTER INVEST AS?

CHRISTIAN MELAND
FYRMESTER INVEST AS
NOK 0 rev. · NOK −31,000 profit

FYRMESTER INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FYRMESTER INVEST AS own?

FYRMESTER INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FYRMESTER INVEST AS

Who owns FYRMESTER INVEST AS?

CHRISTIAN MELAND is the largest registered owner, with 100.0%.

What is the revenue of FYRMESTER INVEST AS?

FYRMESTER INVEST AS had revenue of NOK 0 in 2024.

Where is FYRMESTER INVEST AS based?

FYRMESTER INVEST AS has its business address in Trondheim.

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.