BIZTRAC BETA
Accounting and bookkeeping

KOMPLETT REGNSKAP TROMSØ AS

Org. no. 914267625 Limited company (AS) Tromsø Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 402,000
Equity NOK 1.9m
Incorporated 2014
Share capital NOK 100,000

KOMPLETT REGNSKAP TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 914267625. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med tjenester innen regnskapsførsel, bedriftsrådgivning og andre dertilhørende tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 402,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 402,000
Equity
NOK 1.9m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns KOMPLETT REGNSKAP TROMSØ AS?

GUNHILD IRENE HANSSEN
KOMPLETT REGNSKAP TROMSØ AS
NOK 3.6m rev. · NOK 402,000 profit

KOMPLETT REGNSKAP TROMSØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOMPLETT REGNSKAP TROMSØ AS

Who owns KOMPLETT REGNSKAP TROMSØ AS?

GUNHILD IRENE HANSSEN is the largest registered owner, with 50.0%.

What is the revenue of KOMPLETT REGNSKAP TROMSØ AS?

KOMPLETT REGNSKAP TROMSØ AS had revenue of NOK 3.6m in 2024.

Who is the general manager of KOMPLETT REGNSKAP TROMSØ AS?

Gunn Ellen Strand Hansen is registered as general manager of KOMPLETT REGNSKAP TROMSØ AS.

Where is KOMPLETT REGNSKAP TROMSØ AS based?

KOMPLETT REGNSKAP TROMSØ AS has its business address in Tromsdalen.

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.