BIZTRAC BETA
COMPANY REGISTER PROFILE
931638920 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Development of building projects

LØDØEN BYGG AS

Org. no. 931638920 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 47.7m
Operating profit NOK 2.1m
Equity NOK 483,000
Incorporated 2023
Employees 18
Share capital NOK 100,000

LØDØEN BYGG AS is registered as a limited company in Oslo, Oslo with organisation number 931638920. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2023 and has 18 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, oppføring og rehabiltering av bygg, byggteknisk rådgivning og annen virksomhet som herunder naturlig hører.”. The most recent filed accounts, for the 2025 financial year, show NOK 47.7m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 47.7m
▲ +66 %
Operating profit
NOK 2.1m
▲ +3215 %
Equity
NOK 483,000
▲ +561 %
Est. value
NOK 5.0m

Financial health · 2025

Liquidity
1.02
Satisfactory
Current assets ÷ current liabilities
Profitability
21.0%
Very good
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

Who owns LØDØEN BYGG AS?

LØDØEN BYGG AS
NOK 47.7m rev. · NOK 2.1m profit

LØDØEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØDØEN BYGG AS

Who owns LØDØEN BYGG AS?

TØMRERMESTER PETTER LØDØEN AS is the largest registered owner, with 100.0%.

What is the revenue of LØDØEN BYGG AS?

LØDØEN BYGG AS had revenue of NOK 47.7m in 2025.

Who is the general manager of LØDØEN BYGG AS?

Petter Brinch Lødøen is registered as general manager of LØDØEN BYGG AS.

Where is LØDØEN BYGG AS based?

LØDØEN BYGG AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.