BIZTRAC BETA
Retail sale of clothing

MARKEVEIEN 10 AS

Org. no. 930740977 Limited company (AS) Bergen Incorporated 1936 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 6.2m
Equity NOK 11.5m
Incorporated 1936
Share capital NOK 506,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MARKEVEIEN 10 AS is registered as a limited company in Bergen, Vestland with organisation number 930740977. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1936. Registered share capital is NOK 506,000, divided into 4400 shares. The company's stated purpose is: “Drift av eiendommen Markev 8-10 med tilhørende aktiviteter. Kjøp, salg og drift av fast eiendom. Deltakelse i andre selskaper og ellers annen form for næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 6.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 6.2m
Equity
NOK 11.5m
Est. value
NOK 26.1m

Financial health · 2024

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

Who owns MARKEVEIEN 10 AS?

RITEK AS
MARKEVEIEN 10 AS
NOK 9.5m rev. · NOK 6.2m profit

MARKEVEIEN 10 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MARKEVEIEN 10 AS

Who owns MARKEVEIEN 10 AS?

RITEK AS is the largest registered owner, with 100.0%.

What is the revenue of MARKEVEIEN 10 AS?

MARKEVEIEN 10 AS had revenue of NOK 9.5m in 2024.

Who is the general manager of MARKEVEIEN 10 AS?

Bjørn Emil Riis is registered as general manager of MARKEVEIEN 10 AS.

Where is MARKEVEIEN 10 AS based?

MARKEVEIEN 10 AS has its business address in Bergen.

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.