BIZTRAC BETA
Business and other management consultancy activities

KILDAL AS

Org. no. 918798234 Limited company (AS) Strand Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 365,000
Equity NOK 1.1m
Incorporated 2017
Share capital NOK 30,000

KILDAL AS is registered as a limited company in Strand, Rogaland with organisation number 918798234. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet innen forretningsutvikling, ledelse og forbedringsarbeid, samt investeringer i eiendom og aksjer, og delta i andre selskaper og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 365,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 365,000
Equity
NOK 1.1m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns KILDAL AS?

STEFFEN KILDAL
KILDAL AS
NOK 1.1m rev. · NOK 365,000 profit

KILDAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KILDAL AS own?

KILDAL AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KILDAL AS

Who owns KILDAL AS?

STEFFEN KILDAL is the largest registered owner, with 50.0%.

What is the revenue of KILDAL AS?

KILDAL AS had revenue of NOK 1.1m in 2024.

Who is the general manager of KILDAL AS?

Steffen Kildal is registered as general manager of KILDAL AS.

Where is KILDAL AS based?

KILDAL AS has its business address in Jørpeland.

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.