BIZTRAC BETA
Rental and operating of own or leased real estate

AXEL SELLÆGS VEG 2 AS

Org. no. 932716003 Limited company (AS) Steinkjer Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 480,000
Equity NOK 103,000
Incorporated 2023
Share capital NOK 32,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

AXEL SELLÆGS VEG 2 AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 932716003. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 32,000, divided into 400 shares. The company's stated purpose is: “Selskapets virksomhet skal være investering i fast eiendom og annet som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 480,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 480,000
Equity
NOK 103,000
Est. value
NOK 524,000

Financial health · 2024

Liquidity
6.42
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.5%
Not satisfactory
Equity as a share of total capital

Who owns AXEL SELLÆGS VEG 2 AS?

SEILMAKERGATA 1 STEINKJER AS
AXEL SELLÆGS VEG 2 AS
NOK 1.1m rev. · NOK 480,000 profit

AXEL SELLÆGS VEG 2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AXEL SELLÆGS VEG 2 AS

Who owns AXEL SELLÆGS VEG 2 AS?

SEILMAKERGATA 1 STEINKJER AS is the largest registered owner, with 100.0%.

What is the revenue of AXEL SELLÆGS VEG 2 AS?

AXEL SELLÆGS VEG 2 AS had revenue of NOK 1.1m in 2024.

Where is AXEL SELLÆGS VEG 2 AS based?

AXEL SELLÆGS VEG 2 AS has its business address in Steinkjer.

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.