BIZTRAC BETA
Translation and interpretation activities

COMID AS

Org. no. 920714498 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 52,000
Operating profit NOK 91
Equity NOK 29,000
Incorporated 2018
Share capital NOK 30,000

COMID AS is registered as a limited company in Stavanger, Rogaland with organisation number 920714498. The business is classified under translation and interpretation activities (NACE 74.300). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Levering av PR-, tolke-, oversettelses- og kommunikasjonstjenester (både skriftlige og muntlige), generelle ingeniør- og konsulenttjenester samt salg, drift og utvikling av egne og andre selskapers digitale løsninger og andre tjenester som naturlig hører til dette. Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 52,000 in revenue and NOK 91 in operating profit.

Key figures · 2024

Revenue
NOK 52,000
Operating profit
NOK 91
Equity
NOK 29,000
Est. value
NOK 15,000

Financial health · 2024

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

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

Who owns COMID AS?

IDEAL HAXHIU
COMID AS
NOK 52,000 rev. · NOK 91 profit

COMID AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COMID AS

Who owns COMID AS?

IDEAL HAXHIU is the largest registered owner, with 100.0%.

What is the revenue of COMID AS?

COMID AS had revenue of NOK 52,000 in 2024.

Where is COMID AS based?

COMID AS has its business address in Stavanger.

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.