BIZTRAC BETA
Rental and operating of own or leased real estate

LUMBER NÆRINGSSELSKAP AS

Org. no. 921454228 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.0m
Operating profit NOK 1.4m
Equity NOK 2.0m
Incorporated 2018
Share capital NOK 85,000

Signals

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

LUMBER NÆRINGSSELSKAP AS is registered as a limited company in Kristiansand, Agder with organisation number 921454228. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 85,000, divided into 100 shares. The company's stated purpose is: “Eie, utvikle og leie ut fast eiendom, samt investere i selskaper med tilsvarende formål, og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.0m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.0m
Operating profit
NOK 1.4m
Equity
NOK 2.0m
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.7%
Good
Equity as a share of total capital

Who owns LUMBER NÆRINGSSELSKAP AS?

LUMBER AS
LUMBER NÆRINGSSELSKAP AS
NOK 2.0m rev. · NOK 1.4m profit

LUMBER NÆRINGSSELSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LUMBER NÆRINGSSELSKAP AS

Who owns LUMBER NÆRINGSSELSKAP AS?

LUMBER AS is the largest registered owner, with 100.0%.

What is the revenue of LUMBER NÆRINGSSELSKAP AS?

LUMBER NÆRINGSSELSKAP AS had revenue of NOK 2.0m in 2025.

Where is LUMBER NÆRINGSSELSKAP AS based?

LUMBER NÆRINGSSELSKAP AS has its business address in Kristiansand S.

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.