BIZTRAC BETA
COMPANY REGISTER PROFILE
911759551 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Rental and operating of own or leased real estate

AS FORLAGSHUSET

Org. no. 911759551 Limited company (AS) Oslo Incorporated 1946 Active
Ownership graph ↗
Revenue 2025 NOK 211,000
Operating profit NOK 100,000
Equity NOK 1.5m
Incorporated 1946
Share capital NOK 104,000

AS FORLAGSHUSET is registered as a limited company in Oslo, Oslo with organisation number 911759551. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1946. Registered share capital is NOK 104,000, divided into 74 shares. The company's stated purpose is: “Forlagsvirksomhet og handel samt deltagelse i andre aksjeselskaper. Selskapet kan eie, forvalte, kjøpe og selge fast eiendom samt verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 211,000 in revenue and NOK 100,000 in operating profit.

Key figures · 2025

Revenue
NOK 211,000
Operating profit
NOK 100,000
Equity
NOK 1.5m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns AS FORLAGSHUSET?

KRISTIN LIONÆS
AS FORLAGSHUSET
NOK 211,000 rev. · NOK 100,000 profit

AS FORLAGSHUSET has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AS FORLAGSHUSET

Who owns AS FORLAGSHUSET?

KRISTIN LIONÆS is the largest registered owner, with 67.6%.

What is the revenue of AS FORLAGSHUSET?

AS FORLAGSHUSET had revenue of NOK 211,000 in 2025.

Who is the general manager of AS FORLAGSHUSET?

Kristin Lionæs is registered as general manager of AS FORLAGSHUSET.

Where is AS FORLAGSHUSET based?

AS FORLAGSHUSET 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.