BIZTRAC BETA
Construction of residential and non-residential buildings

PROFF BYGG & VEDLIKEHOLD AS

Org. no. 932298589 Limited company (AS) Porsgrunn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 296,000
Operating profit NOK 171,000
Equity NOK 206,000
Incorporated 2023
Share capital NOK 30,000

PROFF BYGG & VEDLIKEHOLD AS is registered as a limited company in Porsgrunn, Telemark with organisation number 932298589. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Snekker og vedlikeholdsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 296,000 in revenue and NOK 171,000 in operating profit.

Key figures · 2025

Revenue
NOK 296,000
Operating profit
NOK 171,000
Equity
NOK 206,000
Est. value
NOK 615,000

Financial health · 2025

Liquidity
2.87
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
70.5%
Very good
Equity as a share of total capital

Who owns PROFF BYGG & VEDLIKEHOLD AS?

STEFFEN JOHNSEN
PROFF BYGG & VEDLIKEHOLD AS
NOK 296,000 rev. · NOK 171,000 profit

PROFF BYGG & VEDLIKEHOLD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PROFF BYGG & VEDLIKEHOLD AS

Who owns PROFF BYGG & VEDLIKEHOLD AS?

STEFFEN JOHNSEN is the largest registered owner, with 50.0%.

What is the revenue of PROFF BYGG & VEDLIKEHOLD AS?

PROFF BYGG & VEDLIKEHOLD AS had revenue of NOK 296,000 in 2025.

Who is the general manager of PROFF BYGG & VEDLIKEHOLD AS?

Adam Andrzej Bojanowski is registered as general manager of PROFF BYGG & VEDLIKEHOLD AS.

Where is PROFF BYGG & VEDLIKEHOLD AS based?

PROFF BYGG & VEDLIKEHOLD AS has its business address in Porsgrunn.

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.