BIZTRAC BETA
Computer programming activities

LUNNAN AS

Org. no. 987688955 Limited company (AS) Stjørdal Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 278,000
Incorporated 2004
Share capital NOK 100,000

Signals

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

LUNNAN AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 987688955. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utvikling og levering av programvare og digitale tjenester, investering i aksjer og andeler, handel og salg av varer, inkludert drift av nettbutikk, samt all virksomhet som står i nartulig forbindelse med dette, herunder deltakelse i og eierskap i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 278,000
Est. value
NOK 504,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 LUNNAN AS?

RUNE KRISTIAN ALSTAD
LUNNAN AS
NOK 0 rev. · NOK −12,000 profit

LUNNAN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUNNAN AS

Who owns LUNNAN AS?

RUNE KRISTIAN ALSTAD is the largest registered owner, with 100.0%.

What is the revenue of LUNNAN AS?

LUNNAN AS had revenue of NOK 0 in 2025.

Who is the general manager of LUNNAN AS?

Rune Kristian Alstad is registered as general manager of LUNNAN AS.

Where is LUNNAN AS based?

LUNNAN AS has its business address in Hell.

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.