biztrac. BETA
COMPANY REGISTER PROFILE
922087563 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

HOFFMEISTER AS

Org. no. 922087563 Limited company (AS) Melhus Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK −205,000
Equity NOK 1.1m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−205k kr).

HOFFMEISTER AS is registered as a limited company in Melhus, Trøndelag with organisation number 922087563. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av motorkjøretøy, kjøp og salg av profileringsartikler, import og salg av varer, kjøp, salg drift av fast eiendom samt deltagelse i andre selskap direkte eller gjennom eierandeler av ethvert slag.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK −205,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
▼ −19 %
Operating profit
NOK −205,000
▲ +38 %
Equity
NOK 1.1m
▼ −16 %
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns HOFFMEISTER AS?

HOFFMEISTER AS
NOK 5.0m rev. · NOK −205,000 profit

HOFFMEISTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOFFMEISTER AS

Who owns HOFFMEISTER AS?

Terje Hoff is the largest registered owner, with 100.0%.

What is the revenue of HOFFMEISTER AS?

HOFFMEISTER AS had revenue of NOK 5.0m in 2025.

Where is HOFFMEISTER AS based?

HOFFMEISTER AS has its business address in Melhus.

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

Report a problem

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