BIZTRAC BETA
Rental and operating of own or leased real estate

INDUSTRIVEGEN 35 AS

Org. no. 922946051 Limited company (AS) Østre Toten Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 240,000
Operating profit NOK −254,000
Equity NOK 520,000
Incorporated 2019
Share capital NOK 152,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−254k kr).

INDUSTRIVEGEN 35 AS is registered as a limited company in Østre Toten, Innlandet with organisation number 922946051. 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 152,000, divided into 9500 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom samt hva herved måtte stå i forbindelse, herunder deltagelse i andre selskaper. Virksomheten omfatter i tillegg kjøp og salg av verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 240,000 in revenue and NOK −254,000 in operating profit.

Key figures · 2024

Revenue
NOK 240,000
Operating profit
NOK −254,000
Equity
NOK 520,000
Est. value
NOK 715,000

Financial health · 2024

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.8%
Weak
Equity as a share of total capital

Who owns INDUSTRIVEGEN 35 AS?

AT TRAKTOREIENDOM AS
INDUSTRIVEGEN 35 AS
NOK 240,000 rev. · NOK −254,000 profit

INDUSTRIVEGEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDUSTRIVEGEN 35 AS

Who owns INDUSTRIVEGEN 35 AS?

AT TRAKTOREIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of INDUSTRIVEGEN 35 AS?

INDUSTRIVEGEN 35 AS had revenue of NOK 240,000 in 2024.

Where is INDUSTRIVEGEN 35 AS based?

INDUSTRIVEGEN 35 AS has its business address in Lena.

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.