BIZTRAC BETA
Joinery installation

KRISTIAN ROBERTSEN AS

Org. no. 933471071 Limited company (AS) Færder Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 120,000
Equity NOK 152,000
Incorporated 2024
Share capital NOK 30,000

KRISTIAN ROBERTSEN AS is registered as a limited company in Færder, Vestfold with organisation number 933471071. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen snekkerarbeid - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 120,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 120,000
Equity
NOK 152,000
Est. value
NOK 437,000

Financial health · 2025

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

Who owns KRISTIAN ROBERTSEN AS?

KRISTIAN MARINO ALMÈN ROBERTSEN
KRISTIAN ROBERTSEN AS
NOK 1.4m rev. · NOK 120,000 profit

KRISTIAN ROBERTSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KRISTIAN ROBERTSEN AS

Who owns KRISTIAN ROBERTSEN AS?

KRISTIAN MARINO ALMÈN ROBERTSEN is the largest registered owner, with 100.0%.

What is the revenue of KRISTIAN ROBERTSEN AS?

KRISTIAN ROBERTSEN AS had revenue of NOK 1.4m in 2025.

Who is the general manager of KRISTIAN ROBERTSEN AS?

Kristian Marino Almèn Robertsen is registered as general manager of KRISTIAN ROBERTSEN AS.

Where is KRISTIAN ROBERTSEN AS based?

KRISTIAN ROBERTSEN AS has its business address in Husøysund.

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.