biztrac. BETA
COMPANY REGISTER PROFILE
923790535 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Retail sale of footwear and leather goods

ECCO RÅDHUSET AS

Org. no. 923790535 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK −3,000
Equity NOK 127,000
Incorporated 2019
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

ECCO RÅDHUSET AS is registered as a limited company in Oslo, Oslo with organisation number 923790535. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2019 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å drive varer og handel innenfor skotøy, samt det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK −3,000 in operating profit.

Former names: ELVES SMYKKE AS

Key figures · 2025

Revenue
NOK 6.5m
▼ −32 %
Operating profit
NOK −3,000
▼ −100 %
Equity
NOK 127,000
▲ +467 %
Est. value
NOK 578,000

Financial health · 2025

Liquidity
5.45
Very good
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns ECCO RÅDHUSET AS?

ECCO RÅDHUSET AS
NOK 6.5m rev. · NOK −3,000 profit

ECCO RÅDHUSET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ECCO RÅDHUSET AS

Who owns ECCO RÅDHUSET AS?

NORSUND GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of ECCO RÅDHUSET AS?

ECCO RÅDHUSET AS had revenue of NOK 6.5m in 2025.

Where is ECCO RÅDHUSET AS based?

ECCO RÅDHUSET 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.