BIZTRAC BETA
Rental and operating of own or leased real estate

BOGEN OG TAJE UTLEIE AS

Org. no. 996421872 Limited company (AS) Ås Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 360,000
Operating profit NOK 247,000
Equity NOK 1.4m
Incorporated 2011
Share capital NOK 100,000

BOGEN OG TAJE UTLEIE AS is registered as a limited company in Ås, Akershus with organisation number 996421872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av kontorlokaler, inventar og utstyr til trafikkskolevirksomhet og andre tjenester som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 360,000 in revenue and NOK 247,000 in operating profit.

Key figures · 2025

Revenue
NOK 360,000
Operating profit
NOK 247,000
Equity
NOK 1.4m
Est. value
NOK 1.6m

Financial health · 2024

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

Who owns BOGEN OG TAJE UTLEIE AS?

JAN HANSEN TAJE
BOGEN OG TAJE UTLEIE AS
NOK 360,000 rev. · NOK 247,000 profit

BOGEN OG TAJE UTLEIE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOGEN OG TAJE UTLEIE AS

Who owns BOGEN OG TAJE UTLEIE AS?

JAN HANSEN TAJE is the largest registered owner, with 50.0%.

What is the revenue of BOGEN OG TAJE UTLEIE AS?

BOGEN OG TAJE UTLEIE AS had revenue of NOK 360,000 in 2025.

Who is the general manager of BOGEN OG TAJE UTLEIE AS?

Jan Hansen Taje is registered as general manager of BOGEN OG TAJE UTLEIE AS.

Where is BOGEN OG TAJE UTLEIE AS based?

BOGEN OG TAJE UTLEIE AS has its business address in Ås.

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.