BIZTRAC BETA
Manufacture of outerwear

HOT NOK AS

Org. no. 990392412 Limited company (AS) Drammen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 337,000
Operating profit NOK −19,000
Equity NOK 17,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

HOT NOK AS is registered as a limited company in Drammen, Buskerud with organisation number 990392412. The business is classified under manufacture of outerwear (NACE 14.210). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produsere og selge unike ullklær med røtter i norske folkedrakter. Ullklærne skal representere ny design med særegen passform og særegent visuelt uttrykk.”. The most recent filed accounts, for the 2024 financial year, show NOK 337,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 337,000
Operating profit
NOK −19,000
Equity
NOK 17,000
Est. value
NOK 190,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HOT NOK AS?

THEA MARGRETE GLIMSDAL TEMTE
HOT NOK AS
NOK 337,000 rev. · NOK −19,000 profit

HOT NOK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOT NOK AS

Who owns HOT NOK AS?

THEA MARGRETE GLIMSDAL TEMTE is the largest registered owner, with 90.0%.

What is the revenue of HOT NOK AS?

HOT NOK AS had revenue of NOK 337,000 in 2024.

Who is the general manager of HOT NOK AS?

Thea Margrete Glimsdal Temte is registered as general manager of HOT NOK AS.

Where is HOT NOK AS based?

HOT NOK AS has its business address in Solbergelva.

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.