biztrac. BETA
COMPANY REGISTER PROFILE
916810490 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of construction and civil engineering machinery and equipment

LETTVINN AS

Org. no. 916810490 Limited company (AS) Ringerike Incorporated 2016 Active
Revenue 2025 NOK 507,000
Operating profit NOK 33,000
Equity NOK 417,000
Incorporated 2016
Share capital NOK 30,000

LETTVINN AS is registered as a limited company in Ringerike, Buskerud with organisation number 916810490. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapet skal drive med investering i finansielle instrumenter og betalingsmidler samt utleie, salg og kjøp av verktøy og utstyr innen bygg av anlegg. Rådgiving og kursvirksomhet for bruk av verktøy og utstyr i byggebransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 507,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 507,000
▲ +70 %
Operating profit
NOK 33,000
▼ −48 %
Equity
NOK 417,000
▲ +7 %
Est. value
NOK 401,000

Financial health · 2025

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
7.0%
Satisfactory
Return on total assets
Solidity
59.4%
Very good
Equity as a share of total capital

Who owns LETTVINN AS?

LETTVINN AS
NOK 507,000 rev. · NOK 33,000 profit

LETTVINN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LETTVINN AS

Who owns LETTVINN AS?

Andrius Makavicius is the largest registered owner, with 100.0%.

What is the revenue of LETTVINN AS?

LETTVINN AS had revenue of NOK 507,000 in 2025.

Where is LETTVINN AS based?

LETTVINN AS has its business address in Sokna.

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.