BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

INDUSTRITAKSERING AS

Org. no. 843625932 Limited company (AS) Drammen Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 655,000
Equity NOK 2.1m
Incorporated 1987
Share capital NOK 100,000

INDUSTRITAKSERING AS is registered as a limited company in Drammen, Buskerud with organisation number 843625932. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Byggevirksomhet, eie samt utvikle og drive fast eiendom, kjøp og salg av løsøregjenstander, taksering samt deltagelse i dermed beslektede virksomheter samt handel med aksjer og verdipapirer, herunder lånefinansierte investeringer med verdipapirer og valuta. ”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 655,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 655,000
Equity
NOK 2.1m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns INDUSTRITAKSERING AS?

NILS IVAR HOLE
INDUSTRITAKSERING AS
NOK 3.1m rev. · NOK 655,000 profit

INDUSTRITAKSERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDUSTRITAKSERING AS

Who owns INDUSTRITAKSERING AS?

NILS IVAR HOLE is the largest registered owner, with 100.0%.

What is the revenue of INDUSTRITAKSERING AS?

INDUSTRITAKSERING AS had revenue of NOK 3.1m in 2025.

Where is INDUSTRITAKSERING AS based?

INDUSTRITAKSERING AS has its business address in Drammen.

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.