BIZTRAC BETA
Rental and leasing of other personal and household goods

MESSELYS AS

Org. no. 925632988 Limited company (AS) Lillestrøm Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 729,000
Equity NOK 483,000
Incorporated 2020
Share capital NOK 50,000

MESSELYS AS is registered as a limited company in Lillestrøm, Akershus with organisation number 925632988. The business is classified under rental and leasing of other personal and household goods (NACE 77.220). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Utleie og montasje av lysutstyr og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 729,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 729,000
Equity
NOK 483,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.9%
Good
Equity as a share of total capital

Who owns MESSELYS AS?

DANIEL WALMANN MYRVANG
MESSELYS AS
NOK 8.4m rev. · NOK 729,000 profit

MESSELYS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MESSELYS AS

Who owns MESSELYS AS?

DANIEL WALMANN MYRVANG is the largest registered owner, with 50.0%.

What is the revenue of MESSELYS AS?

MESSELYS AS had revenue of NOK 8.4m in 2024.

Who is the general manager of MESSELYS AS?

Daniel Walmann Myrvang is registered as general manager of MESSELYS AS.

Where is MESSELYS AS based?

MESSELYS AS has its business address in Skedsmokorset.

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.