BIZTRAC BETA
COMPANY REGISTER PROFILE
992181397 ORG. NO. 2022 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
On-demand passenger transport service activities by vehicle with driver

JAN HUGO HANSEN

Org. no. 992181397 Sole proprietorship (ENK) Tromsø Active
Ownership graph ↗
Revenue 2022 NOK 3.8m
Operating profit NOK 773,000
Equity NOK 3,000
Employees 7

JAN HUGO HANSEN is registered as a sole proprietorship in Tromsø, Troms with organisation number 992181397. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company has 7 registered employees. The most recent filed accounts, for the 2022 financial year, show NOK 3.8m in revenue and NOK 773,000 in operating profit.

Key figures · 2022

Revenue
NOK 3.8m
Operating profit
NOK 773,000
Equity
NOK 3,000
Est. value
NOK 2.1m

Financial health · 2022

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

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

Who owns JAN HUGO HANSEN?

No shareholders are registered for JAN HUGO HANSEN in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about JAN HUGO HANSEN

What is the revenue of JAN HUGO HANSEN?

JAN HUGO HANSEN had revenue of NOK 3.8m in 2022.

Where is JAN HUGO HANSEN based?

JAN HUGO HANSEN has its business address in Krokelvdalen.

Property

Business address Gabbrovegen 28, 9022 Krokelvdalen
Cadastral unit 5501-14/96/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.