BIZTRAC BETA
Buying and selling of own real estate

LUR INVEST AS

Org. no. 927801760 Limited company (AS) Loppa Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 246,000
Operating profit NOK 9,000
Equity NOK −142,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−142k kr).

LUR INVEST AS is registered as a limited company in Loppa, Finnmark with organisation number 927801760. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av eiendommer, samt tilhørende virksomhet. Selskapet kan tegne seg for eiendeler i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 246,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 246,000
Operating profit
NOK 9,000
Equity
NOK −142,000
Est. value
NOK 99,000

Financial health · 2025

Liquidity
0.68
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-9.9%
Weak
Equity as a share of total capital

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

Who owns LUR INVEST AS?

LYSEFJORD SEAFOOD AS
LUR INVEST AS
NOK 246,000 rev. · NOK 9,000 profit

LUR INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUR INVEST AS

Who owns LUR INVEST AS?

LYSEFJORD SEAFOOD AS is the largest registered owner, with 100.0%.

What is the revenue of LUR INVEST AS?

LUR INVEST AS had revenue of NOK 246,000 in 2025.

Who is the general manager of LUR INVEST AS?

Ove Kenneth Ås is registered as general manager of LUR INVEST AS.

Where is LUR INVEST AS based?

LUR INVEST AS has its business address in Øksfjorden.

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.