BIZTRAC BETA
Auditing

LANGSETH REVISJON AS

Org. no. 995300796 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 20.0m
Operating profit NOK 3.6m
Equity NOK 900,000
Incorporated 2010
Employees 7
Share capital NOK 100,000

LANGSETH REVISJON AS is registered as a limited company in Oslo, Oslo with organisation number 995300796. The business is classified under auditing (NACE 69.201). The company was incorporated in 2010 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Revisjon og rådgivning samt hva som står i naturlig forbindelse, herunder deltagelse i andre selskaper med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.0m in revenue and NOK 3.6m in operating profit.

Key figures · 2025

Revenue
NOK 20.0m
Operating profit
NOK 3.6m
Equity
NOK 900,000
Est. value
NOK 16.7m

Financial health · 2025

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

Who owns LANGSETH REVISJON AS?

LANGSETH GRUPPEN AS
LANGSETH REVISJON AS
NOK 20.0m rev. · NOK 3.6m profit

LANGSETH REVISJON AS has 1 registered shareholder:

All shareholders and roles →

Group structure

LANGSETH REVISJON AS er morselskap for 5 datterselskaper:

Frequently asked questions about LANGSETH REVISJON AS

Who owns LANGSETH REVISJON AS?

LANGSETH GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of LANGSETH REVISJON AS?

LANGSETH REVISJON AS had revenue of NOK 20.0m in 2025.

Who is the general manager of LANGSETH REVISJON AS?

Fredrik Wilhelmsen Langseth is registered as general manager of LANGSETH REVISJON AS.

Where is LANGSETH REVISJON AS based?

LANGSETH REVISJON AS has its business address in Oslo.

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.