BIZTRAC BETA
COMPANY REGISTER PROFILE
930164038 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

NALANE AS

Org. no. 930164038 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 17,000
Operating profit NOK −1,000
Equity NOK 21,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

NALANE AS is registered as a limited company in Bergen, Vestland with organisation number 930164038. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holding.”. The most recent filed accounts, for the 2025 financial year, show NOK 17,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 17,000
Operating profit
NOK −1,000
▲ +0 %
Equity
NOK 21,000
▼ −5 %
Est. value
NOK 21,000

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.3%
Weak
Equity as a share of total capital

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

Who owns NALANE AS?

ALEKSANDER ANDERSEN
NALANE AS
NOK 17,000 rev. · NOK −1,000 profit

NALANE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NALANE AS own?

NALANE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NALANE AS

Who owns NALANE AS?

ALEKSANDER ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of NALANE AS?

NALANE AS had revenue of NOK 17,000 in 2025.

Who is the general manager of NALANE AS?

Aleksander Andersen is registered as general manager of NALANE AS.

Where is NALANE AS based?

NALANE AS has its business address in Godvik.

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

Report a problem

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