biztrac. BETA
COMPANY REGISTER PROFILE
932408635 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Manufacture of other parts and accessories for motor vehicles

LAFINTO DRAMMEN AS

Org. no. 932408635 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 10.9m
Operating profit NOK 979,000
Equity NOK 2.7m
Incorporated 2023
Share capital NOK 30,000

LAFINTO DRAMMEN AS is registered as a limited company in Oslo, Oslo with organisation number 932408635. The business is classified under manufacture of other parts and accessories for motor vehicles (NACE 29.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Påbygging, ombygging, tilbehør og innredninger for vare- og personbiler.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.9m in revenue and NOK 979,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.9m
▲ +14 %
Operating profit
NOK 979,000
▼ −14 %
Equity
NOK 2.7m
▲ +40 %
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
3.24
Very good
Current assets ÷ current liabilities
Profitability
23.8%
Very good
Return on total assets
Solidity
69.6%
Very good
Equity as a share of total capital

Who owns LAFINTO DRAMMEN AS?

LAFINTO DRAMMEN AS
NOK 10.9m rev. · NOK 979,000 profit

LAFINTO DRAMMEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LAFINTO DRAMMEN AS

Who owns LAFINTO DRAMMEN AS?

SELMER CAPITAL AS is the largest registered owner, with 50.0%.

What is the revenue of LAFINTO DRAMMEN AS?

LAFINTO DRAMMEN AS had revenue of NOK 10.9m in 2025.

Who is the general manager of LAFINTO DRAMMEN AS?

Jarl Andre Lindvig is registered as general manager of LAFINTO DRAMMEN AS.

Where is LAFINTO DRAMMEN AS based?

LAFINTO DRAMMEN AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.