BIZTRAC BETA
Development of building projects

KILSUND AS

Org. no. 854525182 Limited company (AS) Bærum Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −835,000
Equity NOK 37.9m
Incorporated 1989
Share capital NOK 500,000

Signals

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

KILSUND AS is registered as a limited company in Bærum, Akershus with organisation number 854525182. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1989. Registered share capital is NOK 500,000, divided into 400 shares. The company's stated purpose is: “Eiendomsdrift, investering i andre selskaper, pengeplassering, samt hba som hører i forbindelse hermed.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −835,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −835,000
Equity
NOK 37.9m
Est. value
NOK 34.4m

Financial health · 2024

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

Who owns KILSUND AS?

ØYVIND JOHAN GEDDE
KILSUND AS
NOK 10,000 rev. · NOK −835,000 profit

KILSUND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KILSUND AS own?

KILSUND AS holds stakes in 18 companies:

See the full ownership structure →

Frequently asked questions about KILSUND AS

Who owns KILSUND AS?

ØYVIND JOHAN GEDDE is the largest registered owner, with 100.0%.

What is the revenue of KILSUND AS?

KILSUND AS had revenue of NOK 10,000 in 2024.

Who is the general manager of KILSUND AS?

Øyvind Johan Gedde is registered as general manager of KILSUND AS.

Where is KILSUND AS based?

KILSUND AS has its business address in Hosle.

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.