BIZTRAC BETA
COMPANY REGISTER PROFILE
930378712 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

LANGSETH AS

Org. no. 930378712 Limited company (AS) Nordre Follo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK 249,000
Incorporated 2022
Share capital NOK 40,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

LANGSETH AS is registered as a limited company in Nordre Follo, Akershus with organisation number 930378712. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 40,000, divided into 60 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −10,000
Equity
NOK 249,000
Est. value
NOK 293,000

Financial health · 2025

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

Who owns LANGSETH AS?

LANGSETH AS
· NOK −10,000 profit

LANGSETH AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LANGSETH AS own?

LANGSETH AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LANGSETH AS

Who owns LANGSETH AS?

MARIUS FORSMO LANGSETH is the largest registered owner, with 100.0%.

Where is LANGSETH AS based?

LANGSETH AS has its business address in Ski.

Property

Business address Finstad hageby 59, 1423 Ski
Cadastral unit 3207-137/738/0/0
Building Rekkehus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.