BIZTRAC BETA
Intermediation service activities for specialised retail sale

NYLÆNDER AS

Org. no. 914851920 Limited company (AS) Kongsvinger Incorporated 1932 Active
Ownership graph ↗
Revenue 2025 NOK 51,000
Operating profit NOK −51,000
Equity NOK 31,000
Incorporated 1932
Share capital NOK 332,000

Signals

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

NYLÆNDER AS is registered as a limited company in Kongsvinger, Innlandet with organisation number 914851920. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 1932. Registered share capital is NOK 332,000. The company's stated purpose is: “Glassmagasin og hva som står i forbindelse med dette. Selskapet kan dessuten delta økonomisk i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 51,000 in revenue and NOK −51,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK −51,000
Equity
NOK 31,000
Est. value
NOK 233,000

Financial health · 2024

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

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

Who owns NYLÆNDER AS?

SVEN OLUF NYLÆNDER
NYLÆNDER AS
NOK 51,000 rev. · NOK −51,000 profit

NYLÆNDER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NYLÆNDER AS

Who owns NYLÆNDER AS?

SVEN OLUF NYLÆNDER is the largest registered owner, with 97.7%.

What is the revenue of NYLÆNDER AS?

NYLÆNDER AS had revenue of NOK 51,000 in 2025.

Who is the general manager of NYLÆNDER AS?

Sven Oluf Nylænder is registered as general manager of NYLÆNDER AS.

Where is NYLÆNDER AS based?

NYLÆNDER AS has its business address in Kongsvinger.

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.