BIZTRAC BETA
Non-specialised wholesale trade

RAVSTEDHUS - EDELTEK AS

Org. no. 985134774 Limited company (AS) Frogn Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 10.3m
Operating profit NOK 2.1m
Equity NOK 2.2m
Incorporated 2002
Share capital NOK 500,000

RAVSTEDHUS - EDELTEK AS is registered as a limited company in Frogn, Akershus with organisation number 985134774. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 2002. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Import, eksport, kjøp og salg av kunst- og håndverksrelaterte produkter, kursvirksomhet og alt som er naturlig forbundet med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.3m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 10.3m
Operating profit
NOK 2.1m
Equity
NOK 2.2m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns RAVSTEDHUS - EDELTEK AS?

RAVSTEDHUS APS
RAVSTEDHUS - EDELTEK AS
NOK 10.3m rev. · NOK 2.1m profit

RAVSTEDHUS - EDELTEK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RAVSTEDHUS - EDELTEK AS

Who owns RAVSTEDHUS - EDELTEK AS?

RAVSTEDHUS APS is the largest registered owner, with 100.0%.

What is the revenue of RAVSTEDHUS - EDELTEK AS?

RAVSTEDHUS - EDELTEK AS had revenue of NOK 10.3m in 2024.

Who is the general manager of RAVSTEDHUS - EDELTEK AS?

Flemming Gejl Sørensen is registered as general manager of RAVSTEDHUS - EDELTEK AS.

Where is RAVSTEDHUS - EDELTEK AS based?

RAVSTEDHUS - EDELTEK AS has its business address in Drøbak.

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.