biztrac. BETA
COMPANY REGISTER PROFILE
934139666 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

VARME OG SIKKERHET AS

Org. no. 934139666 Limited company (AS) Vestby Incorporated 2024 Active
Revenue 2025 NOK 1.1m
Operating profit NOK 253,000
Equity NOK 298,000
Incorporated 2024
Share capital NOK 30,000

VARME OG SIKKERHET AS is registered as a limited company in Vestby, Akershus with organisation number 934139666. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av bil. Elektrisk installasjon. Montering og service av varmepumper. Salg av brukte ting.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 253,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +302 %
Operating profit
NOK 253,000
▲ +131 %
Equity
NOK 298,000
▲ +171 %
Est. value
NOK 804,000

Financial health · 2025

Liquidity
2.88
Very good
Current assets ÷ current liabilities
Profitability
68.5%
Very good
Return on total assets
Solidity
56.6%
Very good
Equity as a share of total capital

Who owns VARME OG SIKKERHET AS?

VARME OG SIKKERHET AS
NOK 1.1m rev. · NOK 253,000 profit

VARME OG SIKKERHET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VARME OG SIKKERHET AS

Who owns VARME OG SIKKERHET AS?

Lene Wold is the largest registered owner, with 100.0%.

What is the revenue of VARME OG SIKKERHET AS?

VARME OG SIKKERHET AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VARME OG SIKKERHET AS?

Lene Wold is registered as general manager of VARME OG SIKKERHET AS.

Where is VARME OG SIKKERHET AS based?

VARME OG SIKKERHET AS has its business address in Son.

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.