BIZTRAC BETA
Uoppgitt

LANGESÆTER HOLDING AS

Org. no. 935641152 Limited company (AS) Kristiansand Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 773,000
Operating profit NOK 4,000
Equity NOK 33,000
Incorporated 2025
Share capital NOK 30,000

LANGESÆTER HOLDING AS is registered as a limited company in Kristiansand, Agder with organisation number 935641152. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å tilby konsulenttjenester, eie aksjer i andre selskaper, kapitalforvaltning og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 773,000 in revenue and NOK 4,000 in operating profit.

Key figures · 2025

Revenue
NOK 773,000
Operating profit
NOK 4,000
Equity
NOK 33,000
Est. value
NOK 38,000

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LANGESÆTER HOLDING AS?

JACOB BERG LANGESÆTER
LANGESÆTER HOLDING AS
NOK 773,000 rev. · NOK 4,000 profit

LANGESÆTER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGESÆTER HOLDING AS

Who owns LANGESÆTER HOLDING AS?

JACOB BERG LANGESÆTER is the largest registered owner, with 100.0%.

What is the revenue of LANGESÆTER HOLDING AS?

LANGESÆTER HOLDING AS had revenue of NOK 773,000 in 2025.

Who is the general manager of LANGESÆTER HOLDING AS?

Jacob Berg Langesæter is registered as general manager of LANGESÆTER HOLDING AS.

Where is LANGESÆTER HOLDING AS based?

LANGESÆTER HOLDING AS has its business address in Kristiansand S.

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.