BIZTRAC BETA
Joinery installation

VINKEL BYGG OG RØR AS

Org. no. 930780839 Limited company (AS) Nordre Follo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 285,000
Equity NOK 391,000
Incorporated 2023
Share capital NOK 40,000

VINKEL BYGG OG RØR AS is registered as a limited company in Nordre Follo, Akershus with organisation number 930780839. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Innvendig og utvendig oppussing av hus, leilighet og hytte. Rehabilitering av eiendom. Herunder snekring, maling, murerarbeid og andre tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 285,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 285,000
Equity
NOK 391,000
Est. value
NOK 1.1m

Financial health · 2024

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

Who owns VINKEL BYGG OG RØR AS?

NEXHMEDIN GJYLANI
VINKEL BYGG OG RØR AS
NOK 2.9m rev. · NOK 285,000 profit

VINKEL BYGG OG RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINKEL BYGG OG RØR AS

Who owns VINKEL BYGG OG RØR AS?

NEXHMEDIN GJYLANI is the largest registered owner, with 100.0%.

What is the revenue of VINKEL BYGG OG RØR AS?

VINKEL BYGG OG RØR AS had revenue of NOK 2.9m in 2024.

Where is VINKEL BYGG OG RØR AS based?

VINKEL BYGG OG RØR AS has its business address in Ski.

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.