BIZTRAC BETA
Rental and leasing of agricultural machinery and equipment

TH. AGRO AS

Org. no. 985945381 Limited company (AS) Indre Fosen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 331,000
Incorporated 2003
Share capital NOK 102,000

Signals

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

TH. AGRO AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 985945381. The business is classified under rental and leasing of agricultural machinery and equipment (NACE 77.310). The company was incorporated in 2003. Registered share capital is NOK 102,000, divided into 102000 shares. The company's stated purpose is: “Utleie av utstyr innen landbruk, kjøp og salg av varer og tjenester, kjøp og salg av aksjer og verdipapirer, eie og forvalte fast eiendom samt være delaktig i tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 331,000
Est. value
NOK 476,000

Financial health · 2024

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

Who owns TH. AGRO AS?

JOMAR LEIRA
TH. AGRO AS
NOK 0 rev. · NOK −8,000 profit

TH. AGRO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TH. AGRO AS

Who owns TH. AGRO AS?

JOMAR LEIRA is the largest registered owner, with 100.0%.

What is the revenue of TH. AGRO AS?

TH. AGRO AS had revenue of NOK 0 in 2024.

Who is the general manager of TH. AGRO AS?

Jomar Leira is registered as general manager of TH. AGRO AS.

Where is TH. AGRO AS based?

TH. AGRO AS has its business address in Rissa.

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.