BIZTRAC BETA
Intermediation service activities for real estate activities

RØYKEN OG OMEGN EIENDOM AS

Org. no. 913351681 Limited company (AS) Asker Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 4,000
Equity NOK 222,000
Incorporated 2014
Share capital NOK 100,000

RØYKEN OG OMEGN EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 913351681. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendomsmegling samt virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 4,000
Equity
NOK 222,000
Est. value
NOK 164,000

Financial health · 2025

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

Who owns RØYKEN OG OMEGN EIENDOM AS?

MARTIN TVERDAL
RØYKEN OG OMEGN EIENDOM AS
NOK 1.0m rev. · NOK 4,000 profit

RØYKEN OG OMEGN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØYKEN OG OMEGN EIENDOM AS

Who owns RØYKEN OG OMEGN EIENDOM AS?

MARTIN TVERDAL is the largest registered owner, with 100.0%.

What is the revenue of RØYKEN OG OMEGN EIENDOM AS?

RØYKEN OG OMEGN EIENDOM AS had revenue of NOK 1.0m in 2025.

Who is the general manager of RØYKEN OG OMEGN EIENDOM AS?

Martin Tverdal is registered as general manager of RØYKEN OG OMEGN EIENDOM AS.

Where is RØYKEN OG OMEGN EIENDOM AS based?

RØYKEN OG OMEGN EIENDOM AS has its business address in Spikkestad.

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.