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

INNHERRED TAKST AS

Org. no. 931124617 Limited company (AS) Verdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 276,000
Operating profit NOK 61,000
Equity NOK 69,000
Incorporated 2023
Share capital NOK 40,000

INNHERRED TAKST AS is registered as a limited company in Verdal, Trøndelag with organisation number 931124617. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Taksering av boliger og andre tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 276,000 in revenue and NOK 61,000 in operating profit.

Key figures · 2024

Revenue
NOK 276,000
Operating profit
NOK 61,000
Equity
NOK 69,000
Est. value
NOK 206,000

Financial health · 2024

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

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

Who owns INNHERRED TAKST AS?

OLE KRISTIAN SKROVE
INNHERRED TAKST AS
NOK 276,000 rev. · NOK 61,000 profit

INNHERRED TAKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INNHERRED TAKST AS

Who owns INNHERRED TAKST AS?

OLE KRISTIAN SKROVE is the largest registered owner, with 100.0%.

What is the revenue of INNHERRED TAKST AS?

INNHERRED TAKST AS had revenue of NOK 276,000 in 2024.

Where is INNHERRED TAKST AS based?

INNHERRED TAKST AS has its business address in Verdal.

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.