biztrac. BETA
COMPANY REGISTER PROFILE
917126402 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other cleaning activities

SVENDSEN & BRÅTLUND AS

Org. no. 917126402 Limited company (AS) Arendal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 454,000
Operating profit NOK 55,000
Equity NOK 882,000
Incorporated 2016
Share capital NOK 30,000

SVENDSEN & BRÅTLUND AS is registered as a limited company in Arendal, Agder with organisation number 917126402. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Markarbeid med entreprenørmaskiner og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 454,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 454,000
▼ −36 %
Operating profit
NOK 55,000
▼ −48 %
Equity
NOK 882,000
▲ +5 %
Est. value
NOK 743,000

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
3.9%
Weak
Return on total assets
Solidity
60.8%
Very good
Equity as a share of total capital

Who owns SVENDSEN & BRÅTLUND AS?

SVENDSEN & BRÅTLUND AS
NOK 454,000 rev. · NOK 55,000 profit

SVENDSEN & BRÅTLUND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVENDSEN & BRÅTLUND AS

Who owns SVENDSEN & BRÅTLUND AS?

Allan Bråtlund is the largest registered owner, with 50.0%.

What is the revenue of SVENDSEN & BRÅTLUND AS?

SVENDSEN & BRÅTLUND AS had revenue of NOK 454,000 in 2025.

Who is the general manager of SVENDSEN & BRÅTLUND AS?

Michael Ørjan Svendsen is registered as general manager of SVENDSEN & BRÅTLUND AS.

Where is SVENDSEN & BRÅTLUND AS based?

SVENDSEN & BRÅTLUND AS has its business address in Bjorbekk.

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

Report a problem

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