BIZTRAC BETA
Other real estate activities on a fee or contract basis

ICON TAKST AS

Org. no. 899504062 Limited company (AS) Løten Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −366,000
Equity NOK 969,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−366k kr).

ICON TAKST AS is registered as a limited company in Løten, Innlandet with organisation number 899504062. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Taksering av eiendom, konsulentvirksomhet innen eiendom, herunder produksjon, oppføring og restaurering av boliger samt investeringsviksomhet i aksjer og andeler i andre selskaper, herunder eie og forvalte verdipapirer og hva derved står i sammenheng.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −366,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −366,000
Equity
NOK 969,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns ICON TAKST AS?

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

Frequently asked questions about ICON TAKST AS

What is the revenue of ICON TAKST AS?

ICON TAKST AS had revenue of NOK 1.4m in 2024.

Who is the general manager of ICON TAKST AS?

Rune Juvet Kirkerud is registered as general manager of ICON TAKST AS.

Where is ICON TAKST AS based?

ICON TAKST AS has its business address in Løten.

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.