biztrac. BETA
COMPANY REGISTER PROFILE
935090318 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

LANGRYGGEN INVEST AS

Org. no. 935090318 Limited company (AS) Vestvågøy Incorporated 2025 Active
Revenue 2025 NOK 0
Operating profit NOK −79,000
Equity NOK 23.6m
Incorporated 2025
Share capital NOK 300,000

Signals

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

LANGRYGGEN INVEST AS is registered as a limited company in Vestvågøy, Nordland with organisation number 935090318. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 300,000, divided into 300000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper. I tillegg kan selskapet direkte investere og eie eiendom samt drive eiendomsdrift.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −79,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −79,000
Equity
NOK 23.6m
Est. value
NOK 15.1m

Financial health · 2025

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

Who owns LANGRYGGEN INVEST AS?

LANGRYGGEN INVEST AS
NOK 0 rev. · NOK −79,000 profit

LANGRYGGEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGRYGGEN INVEST AS

Who owns LANGRYGGEN INVEST AS?

Remi André Unstad is the largest registered owner, with 100.0%.

What is the revenue of LANGRYGGEN INVEST AS?

LANGRYGGEN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of LANGRYGGEN INVEST AS?

Remi André Unstad is registered as general manager of LANGRYGGEN INVEST AS.

Where is LANGRYGGEN INVEST AS based?

LANGRYGGEN INVEST AS has its business address in Sennesvik.

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

Report a problem

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