BIZTRAC BETA
Rental and operating of own or leased real estate

HOVIN FLEIRBRUKSHUS AS

Org. no. 979878036 Limited company (AS) Tinn Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 309,000
Operating profit NOK −50,000
Equity NOK 1.7m
Incorporated 1998
Share capital NOK 1.7m

Signals

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

HOVIN FLEIRBRUKSHUS AS is registered as a limited company in Tinn, Telemark with organisation number 979878036. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 1.7m, divided into 1725 shares. The company's stated purpose is: “Eie og leie ut lokaler og bensinstasjon i Hovin.”. The most recent filed accounts, for the 2024 financial year, show NOK 309,000 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 309,000
Operating profit
NOK −50,000
Equity
NOK 1.7m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns HOVIN FLEIRBRUKSHUS AS?

TINN KOMMUNE
HOVIN FLEIRBRUKSHUS AS
NOK 309,000 rev. · NOK −50,000 profit

HOVIN FLEIRBRUKSHUS AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about HOVIN FLEIRBRUKSHUS AS

Who owns HOVIN FLEIRBRUKSHUS AS?

TINN KOMMUNE is the largest registered owner, with 11.6%.

What is the revenue of HOVIN FLEIRBRUKSHUS AS?

HOVIN FLEIRBRUKSHUS AS had revenue of NOK 309,000 in 2024.

Who is the general manager of HOVIN FLEIRBRUKSHUS AS?

Tor Helge Flåto is registered as general manager of HOVIN FLEIRBRUKSHUS AS.

Where is HOVIN FLEIRBRUKSHUS AS based?

HOVIN FLEIRBRUKSHUS AS has its business address in Hovin I Telemark.

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.