BIZTRAC BETA
COMPANY REGISTER PROFILE
970142223 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 02.09.2026
Support activities for animal production

TYR

Org. no. 970142223 Association/club/organisation (FLI) Hamar Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 36.5m
Operating profit NOK 643,000
Equity NOK 13.7m
Incorporated 1995
Employees 11

TYR is registered as a association/club/organisation in Hamar, Innlandet with organisation number 970142223. The business is classified under support activities for animal production (NACE 01.620). The company was incorporated in 1995 and has 11 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 36.5m in revenue and NOK 643,000 in operating profit.

Former names: NORSK KJØTTFEAVLSLAG

Key figures · 2025

Revenue
NOK 36.5m
Operating profit
NOK 643,000
Equity
NOK 13.7m
Est. value
NOK 10.7m

Financial health · 2025

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

Who owns TYR?

No shareholders are registered for TYR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TYR

What is the revenue of TYR?

TYR had revenue of NOK 36.5m in 2025.

Who is the general manager of TYR?

Per-Sigve Lien is registered as general manager of TYR.

Where is TYR based?

TYR has its business address in Hamar.

Property

Business address Storhamargata 44, 2317 Hamar
Cadastral unit 3403-1/37/0/0

27 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.