biztrac. BETA
COMPANY REGISTER PROFILE
921378947 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of textiles

GARNHEXENE AS

Org. no. 921378947 Limited company (AS) Horten Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK 83,000
Equity NOK 249,000
Incorporated 2018
Employees 5
Share capital NOK 1.0m

GARNHEXENE AS is registered as a limited company in Horten, Vestfold with organisation number 921378947. The business is classified under retail sale of textiles (NACE 47.510). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 1.0m, divided into 10040 shares. The company's stated purpose is: “Butikk- og netthandel med tekstiler og utstyrsvarer, strikking, hekling, håndarbeid, veveri og hobbyvirksomhet og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet og kjøp og salg av aksjer eller annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK 83,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
▲ +7 %
Operating profit
NOK 83,000
▲ +117 %
Equity
NOK 249,000
▲ +45 %
Est. value
NOK 507,000

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
14.6%
Satisfactory
Equity as a share of total capital

Who owns GARNHEXENE AS?

GARNHEXENE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about GARNHEXENE AS

Who owns GARNHEXENE AS?

Jannie Richardsen is the largest registered owner, with 77.7%.

What is the revenue of GARNHEXENE AS?

GARNHEXENE AS had revenue of NOK 2.2m in 2025.

Where is GARNHEXENE AS based?

GARNHEXENE AS has its business address in Horten.

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.