BIZTRAC BETA
Repair and maintenance of machinery

KIS MARITIME AS

Org. no. 977485258 Limited company (AS) Bergen Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 46.9m
Operating profit NOK 4.4m
Equity NOK 3.5m
Incorporated 1997
Employees 17
Share capital NOK 150,000

KIS MARITIME AS is registered as a limited company in Bergen, Vestland with organisation number 977485258. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1997 and has 17 registered employees. Registered share capital is NOK 150,000. The company's stated purpose is: “Salg og service av løfteinnretninger og beslektede produkter og hva som naturlig står i forbindelse med dette. Selskapet har anledning til å kjøpe seg inn i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 46.9m in revenue and NOK 4.4m in operating profit.

Key figures · 2024

Revenue
NOK 46.9m
Operating profit
NOK 4.4m
Equity
NOK 3.5m
Est. value
NOK 18.4m

Financial health · 2024

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.0%
Good
Equity as a share of total capital

Who owns KIS MARITIME AS?

KIS PARTNERS AS
KIS MARITIME AS
NOK 46.9m rev. · NOK 4.4m profit

KIS MARITIME AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KIS MARITIME AS er morselskap for 10 datterselskaper:

Frequently asked questions about KIS MARITIME AS

Who owns KIS MARITIME AS?

KIS PARTNERS AS is the largest registered owner, with 100.0%.

What is the revenue of KIS MARITIME AS?

KIS MARITIME AS had revenue of NOK 46.9m in 2024.

Who is the general manager of KIS MARITIME AS?

Birger André Hansen is registered as general manager of KIS MARITIME AS.

Where is KIS MARITIME AS based?

KIS MARITIME AS has its business address in Hylkje.

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.