BIZTRAC BETA
Computer programming activities

SVEIN MAGNAR NYLUND AS

Org. no. 931718460 Limited company (AS) Ibestad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 12,000
Operating profit NOK 9,000
Equity NOK 38,000
Incorporated 2023
Share capital NOK 30,000

SVEIN MAGNAR NYLUND AS is registered as a limited company in Ibestad, Troms with organisation number 931718460. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Programmeringstjenester og investering i andre selskaper, samt virksomhet som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 12,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 12,000
Operating profit
NOK 9,000
Equity
NOK 38,000
Est. value
NOK 47,000

Financial health · 2024

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

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

Who owns SVEIN MAGNAR NYLUND AS?

SVEIN MAGNAR NYLUND
SVEIN MAGNAR NYLUND AS
NOK 12,000 rev. · NOK 9,000 profit

SVEIN MAGNAR NYLUND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVEIN MAGNAR NYLUND AS own?

SVEIN MAGNAR NYLUND AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVEIN MAGNAR NYLUND AS

Who owns SVEIN MAGNAR NYLUND AS?

SVEIN MAGNAR NYLUND is the largest registered owner, with 96.5%.

What is the revenue of SVEIN MAGNAR NYLUND AS?

SVEIN MAGNAR NYLUND AS had revenue of NOK 12,000 in 2024.

Where is SVEIN MAGNAR NYLUND AS based?

SVEIN MAGNAR NYLUND AS has its business address in Engenes.

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.