BIZTRAC BETA
Rental and operating of own or leased real estate

LØVEGEN 1 AS

Org. no. 924302240 Limited company (AS) Namsos Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 412,000
Equity NOK 4.3m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

LØVEGEN 1 AS is registered as a limited company in Namsos, Trøndelag with organisation number 924302240. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 1000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, herunder drive utvikling av eiendom, samt virksomhet beslektet med dette, og deltagelse i andre selskaper med virksomhet som naturlig står i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 412,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 412,000
Equity
NOK 4.3m
Est. value
NOK 3.9m

Financial health · 2025

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

Who owns LØVEGEN 1 AS?

MIDTRE NAMDAL AVFALLSSELSKAP IKS
LØVEGEN 1 AS
NOK 1.3m rev. · NOK 412,000 profit

LØVEGEN 1 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVEGEN 1 AS

Who owns LØVEGEN 1 AS?

MIDTRE NAMDAL AVFALLSSELSKAP IKS is the largest registered owner, with 100.0%.

What is the revenue of LØVEGEN 1 AS?

LØVEGEN 1 AS had revenue of NOK 1.3m in 2025.

Where is LØVEGEN 1 AS based?

LØVEGEN 1 AS has its business address in Spillum.

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.