BIZTRAC BETA
Publishing of journals and periodicals

BYGGFORLAGET AS

Org. no. 921730675 Limited company (AS) Oslo Incorporated 1967 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 1.2m
Equity NOK 2.2m
Incorporated 1967
Share capital NOK 120,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BYGGFORLAGET AS is registered as a limited company in Oslo, Oslo with organisation number 921730675. The business is classified under publishing of journals and periodicals (NACE 58.130). The company was incorporated in 1967. Registered share capital is NOK 120,000. The company's stated purpose is: “Drive forlagsvirksomhet og annen dermed beslektet virksomhet, samt deltagelse i andre selskaper, dessuten virke som service-organ for Norges Byggmesterforbund.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 1.2m
Equity
NOK 2.2m
Est. value
NOK 7.6m

Financial health · 2024

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

Who owns BYGGFORLAGET AS?

BYGGMESTERFORBUNDET
BYGGFORLAGET AS
NOK 5.0m rev. · NOK 1.2m profit

BYGGFORLAGET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BYGGFORLAGET AS

Who owns BYGGFORLAGET AS?

BYGGMESTERFORBUNDET is the largest registered owner, with 91.6%.

What is the revenue of BYGGFORLAGET AS?

BYGGFORLAGET AS had revenue of NOK 5.0m in 2024.

Who is the general manager of BYGGFORLAGET AS?

Christopher Kunøe is registered as general manager of BYGGFORLAGET AS.

Where is BYGGFORLAGET AS based?

BYGGFORLAGET 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 15.06.2026.

Report a problem

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