BIZTRAC BETA
Construction of residential and non-residential buildings

BYGGMESTER ERLEND CUDRIO AS

Org. no. 917100845 Limited company (AS) Færder Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 7.2m
Operating profit NOK 439,000
Equity NOK 876,000
Incorporated 2016
Share capital NOK 30,000

BYGGMESTER ERLEND CUDRIO AS is registered as a limited company in Færder, Vestfold with organisation number 917100845. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring/rehabilitering av bygg, eiendomsutvikling og takstvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.2m in revenue and NOK 439,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.2m
Operating profit
NOK 439,000
Equity
NOK 876,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns BYGGMESTER ERLEND CUDRIO AS?

ERLEND CUDRIO
BYGGMESTER ERLEND CUDRIO AS
NOK 7.2m rev. · NOK 439,000 profit

BYGGMESTER ERLEND CUDRIO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYGGMESTER ERLEND CUDRIO AS

Who owns BYGGMESTER ERLEND CUDRIO AS?

ERLEND CUDRIO is the largest registered owner, with 100.0%.

What is the revenue of BYGGMESTER ERLEND CUDRIO AS?

BYGGMESTER ERLEND CUDRIO AS had revenue of NOK 7.2m in 2025.

Who is the general manager of BYGGMESTER ERLEND CUDRIO AS?

Erlend Cudrio is registered as general manager of BYGGMESTER ERLEND CUDRIO AS.

Where is BYGGMESTER ERLEND CUDRIO AS based?

BYGGMESTER ERLEND CUDRIO AS has its business address in Duken.

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.