BIZTRAC BETA
Civil engineering activities

OSLO TAKSTKONTOR AS

Org. no. 914773059 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 55,000
Operating profit NOK 36,000
Equity NOK 40,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-11 Adresseendring registrert 2026-06-11.

OSLO TAKSTKONTOR AS is registered as a limited company in Oslo, Oslo with organisation number 914773059. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tjenesteyting, servicetilbyder og kontorfellesskap for byggmestre og takstmenn. Herunder tekniske tilstandsanalyser, verditaksering, skattetaksering, skadetaksering og annet som er relevant for bransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 55,000 in revenue and NOK 36,000 in operating profit.

Key figures · 2025

Revenue
NOK 55,000
Operating profit
NOK 36,000
Equity
NOK 40,000
Est. value
NOK 135,000

Financial health · 2025

Liquidity
1.81
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OSLO TAKSTKONTOR AS?

MAXIMERE NORGE AS
OSLO TAKSTKONTOR AS
NOK 55,000 rev. · NOK 36,000 profit

OSLO TAKSTKONTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSLO TAKSTKONTOR AS

Who owns OSLO TAKSTKONTOR AS?

MAXIMERE NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of OSLO TAKSTKONTOR AS?

OSLO TAKSTKONTOR AS had revenue of NOK 55,000 in 2025.

Where is OSLO TAKSTKONTOR AS based?

OSLO TAKSTKONTOR 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.