BIZTRAC BETA
Computer consultancy and computer facilities management activities

HATFACTORY AS

Org. no. 915104096 Limited company (AS) Bærum Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 16,000
Operating profit NOK −25,000
Equity NOK 424,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

HATFACTORY AS is registered as a limited company in Bærum, Akershus with organisation number 915104096. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Konsulentvirksomhet innenfor informasjonsteknologi, finansielle investeringer samt annen virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
Operating profit
NOK −25,000
Equity
NOK 424,000
Est. value
NOK 219,000

Financial health · 2025

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

Who owns HATFACTORY AS?

KARL JAKOB LIND
HATFACTORY AS
NOK 16,000 rev. · NOK −25,000 profit

HATFACTORY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HATFACTORY AS

Who owns HATFACTORY AS?

KARL JAKOB LIND is the largest registered owner, with 100.0%.

What is the revenue of HATFACTORY AS?

HATFACTORY AS had revenue of NOK 16,000 in 2025.

Who is the general manager of HATFACTORY AS?

Karl Jakob Lind is registered as general manager of HATFACTORY AS.

Where is HATFACTORY AS based?

HATFACTORY AS has its business address in Fornebu.

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.