BIZTRAC BETA
Development of building projects

IKR INGENIØRKONTOR AS

Org. no. 991326278 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 841,000
Operating profit NOK 446,000
Equity NOK 395,000
Incorporated 2007
Share capital NOK 30,000

IKR INGENIØRKONTOR AS is registered as a limited company in Stavanger, Rogaland with organisation number 991326278. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2007. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling, samt lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 841,000 in revenue and NOK 446,000 in operating profit.

Key figures · 2025

Revenue
NOK 841,000
Operating profit
NOK 446,000
Equity
NOK 395,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns IKR INGENIØRKONTOR AS?

KÅRE RØDDE
IKR INGENIØRKONTOR AS
NOK 841,000 rev. · NOK 446,000 profit

IKR INGENIØRKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IKR INGENIØRKONTOR AS own?

IKR INGENIØRKONTOR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about IKR INGENIØRKONTOR AS

Who owns IKR INGENIØRKONTOR AS?

KÅRE RØDDE is the largest registered owner, with 100.0%.

What is the revenue of IKR INGENIØRKONTOR AS?

IKR INGENIØRKONTOR AS had revenue of NOK 841,000 in 2025.

Who is the general manager of IKR INGENIØRKONTOR AS?

Kåre Rødde is registered as general manager of IKR INGENIØRKONTOR AS.

Where is IKR INGENIØRKONTOR AS based?

IKR INGENIØRKONTOR AS has its business address in Stavanger.

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.