BIZTRAC BETA
Rental and operating of own or leased real estate

SØR-VARANGER BILTEKNIKK EIENDOM AS

Org. no. 931572032 Limited company (AS) Sør-Varanger Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 1.8m
Equity NOK 4.8m
Incorporated 2023
Share capital NOK 60,000

SØR-VARANGER BILTEKNIKK EIENDOM AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 931572032. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Drive investering i fast eiendom, utleie av fast eiendom og det som naturlig står i sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 1.8m
Equity
NOK 4.8m
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.8%
Good
Equity as a share of total capital

Who owns SØR-VARANGER BILTEKNIKK EIENDOM AS?

SØR-VARANGER BILTEKNIKK HOLDING AS
SØR-VARANGER BILTEKNIKK EIENDOM AS
NOK 2.7m rev. · NOK 1.8m profit

SØR-VARANGER BILTEKNIKK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØR-VARANGER BILTEKNIKK EIENDOM AS

Who owns SØR-VARANGER BILTEKNIKK EIENDOM AS?

SØR-VARANGER BILTEKNIKK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SØR-VARANGER BILTEKNIKK EIENDOM AS?

SØR-VARANGER BILTEKNIKK EIENDOM AS had revenue of NOK 2.7m in 2025.

Where is SØR-VARANGER BILTEKNIKK EIENDOM AS based?

SØR-VARANGER BILTEKNIKK EIENDOM AS has its business address in Hesseng.

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.