BIZTRAC BETA
Rental and operating of own or leased real estate

LIMEYFY AS

Org. no. 930570095 Limited company (AS) Elverum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −8,000
Equity NOK 39,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

LIMEYFY AS is registered as a limited company in Elverum, Innlandet with organisation number 930570095. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringer i eiendom og verdipapirer herunder aksjer, samt digital produktutvikling og rådgivende virksomhet innenfor nettbaserte løsninger.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −8,000
Equity
NOK 39,000
Est. value
NOK 51,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LIMEYFY AS?

KULVETECH AS
LIMEYFY AS
NOK 16,000 rev. · NOK −8,000 profit

LIMEYFY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LIMEYFY AS

Who owns LIMEYFY AS?

KULVETECH AS is the largest registered owner, with 83.3%.

What is the revenue of LIMEYFY AS?

LIMEYFY AS had revenue of NOK 16,000 in 2025.

Who is the general manager of LIMEYFY AS?

Martin Kulvedrøsten Myhre is registered as general manager of LIMEYFY AS.

Where is LIMEYFY AS based?

LIMEYFY AS has its business address in Elverum.

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.