BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

LUNDBY OG RYGG MASKIN AS

Org. no. 920822223 Limited company (AS) Drammen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 748,000
Equity NOK 2.1m
Incorporated 2018
Share capital NOK 100,000

LUNDBY OG RYGG MASKIN AS is registered as a limited company in Drammen, Buskerud with organisation number 920822223. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av anleggsmaskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 748,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 748,000
Equity
NOK 2.1m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns LUNDBY OG RYGG MASKIN AS?

ALSTAD-RYGG HOLDING AS
LUNDBY OG RYGG MASKIN AS
NOK 3.7m rev. · NOK 748,000 profit

LUNDBY OG RYGG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUNDBY OG RYGG MASKIN AS

Who owns LUNDBY OG RYGG MASKIN AS?

ALSTAD-RYGG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of LUNDBY OG RYGG MASKIN AS?

LUNDBY OG RYGG MASKIN AS had revenue of NOK 3.7m in 2025.

Who is the general manager of LUNDBY OG RYGG MASKIN AS?

Tove Rygg is registered as general manager of LUNDBY OG RYGG MASKIN AS.

Where is LUNDBY OG RYGG MASKIN AS based?

LUNDBY OG RYGG MASKIN AS has its business address in Drammen.

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.