BIZTRAC BETA
COMPANY REGISTER PROFILE
989513729 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other non-specialised retail sale

HENNING TORSTENSEN AS

Org. no. 989513729 Limited company (AS) Andøy Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 145,000
Equity NOK 1.5m
Incorporated 2006
Share capital NOK 100,000

HENNING TORSTENSEN AS is registered as a limited company in Andøy, Nordland with organisation number 989513729. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive handel med maritimt utstyr, samt utføre servicearbeide på samme.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 145,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
▼ −4 %
Operating profit
NOK 145,000
▲ +20060 %
Equity
NOK 1.5m
▲ +6 %
Est. value
NOK 1.3m

Financial health · 2025

Liquidity
3.14
Very good
Current assets ÷ current liabilities
Profitability
5.3%
Weak
Return on total assets
Solidity
58.5%
Very good
Equity as a share of total capital

Who owns HENNING TORSTENSEN AS?

HENNING TORSTENSEN AS
NOK 6.7m rev. · NOK 145,000 profit

HENNING TORSTENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENNING TORSTENSEN AS

Who owns HENNING TORSTENSEN AS?

STIG HENNING TORSTENSEN is the largest registered owner, with 100.0%.

What is the revenue of HENNING TORSTENSEN AS?

HENNING TORSTENSEN AS had revenue of NOK 6.7m in 2025.

Who is the general manager of HENNING TORSTENSEN AS?

Stig Henning Torstensen is registered as general manager of HENNING TORSTENSEN AS.

Where is HENNING TORSTENSEN AS based?

HENNING TORSTENSEN AS has its business address in Andenes.

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

Report a problem

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